"Table or view does not exist" error when launching web if using a standalone security database (Doc ID 784742.1)

Last updated on JANUARY 05, 2017

Applies to:

LODESTAR EIP - Version: 1.5.0 and later   [Release: 1.5 and later ]
Oracle Utilities Meter Data Management - Version: 1.5.0 and later    [Release: 1.5 and later]
Oracle Utilities Billing Component - Version: 1.5.0 and later    [Release: 1.5 and later]
Oracle Utilities Rate Management - Version: 1.5.0 and later    [Release: 1.5 and later]
Oracle Utilities Quotations Management - Version: 1.5.0 and later    [Release: 1.5 and later]
Information in this document applies to any platform.
HealthPlan Action 1476351

Symptoms

The following error occurs when launching the web application:

LSDB5160: Unable to execute stored procedure 'XXXXX.LSP_KILL_EXPR_SESS'
ORA-00942: table or view does not exist

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Runtime.InteropServices.COMException: LSDB5160: Unable to execute stored procedure 'XXXXX.LSP_KILL_EXPR_SESS'
ORA-00942: table or view does not exist


Source Error:

Line 429: public string SSOMode {
Line 430: get {
Line 431: string s = _session.SSOMode;
Line 432: return s;
Line 433: }


Source File: c:\LODESTAR\Web\App_Code\Security\SessionContext.cs Line: 431

Stack Trace:

[COMException (0x900022b4): LSDB5160: Unable to execute stored procedure 'XXXXX.LSP_KILL_EXPR_SESS'
ORA-00942: table or view does not exist
]
Lodestar.Interop.LSSecure.SessionClass.get_SSOMode() +0
Lodestar.Web.Security.SessionContext.get_SSOMode() in c:\LODESTAR\Web\App_Code\Security\SessionContext.cs:431
Lodestar.Web.Security.SessionContext.TrySSO() in c:\LODESTAR\Web\App_Code\Security\SessionContext.cs:163
Default.Page_Load(Object sender, EventArgs e) in c:\LODESTAR\Web\ccs\Default.aspx.cs:36
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +33
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint

Changes

The error we are addressing here occurs only when using a standalone security database. This means that the schema referenced in the lssecure.cfg.xml file was created by running the build scripts with the -security option.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms