ERROR OCCURED AT RECURSIVE SQL LEVEL1 ORA-00942:TABLE OR VIEW DOSEN'T EXIST

Hi every one, I am fresher, I am getting error when I am trying to run my workflow.
My work flow is getting succeeded in my folder and writing 22074 rows same as source qualifier. But yesterday I tried to move it to the other folder by exporting it to my desktop, and again by importing it to the other folder. from then it is not working and giving Table or view does not exist.
My target name is ws_twfs_olb_project_ds but in the session log it is showing wc_twfs_olb_project_ds1 . I really dont know what I have made changes while importing it to the other folder.
Can any one please suggest me how to resolve this issue in Informatica 9.0.1. the only problem I think is the target table is replaced with following "1". Can any one pease help me in it ASAP.
Thanks
Venkat

It has nothing to do with DBMS_XMLGEN.GETXMLTYPE. It simply means user executing your SQL has no select privilege on table &SCHEMA_NAME.&TABLE_NAME.
SY.

Similar Messages

Java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist while invoking a DBAdapter

I have a WebService which is invoked , the request is routed through the mideator to the DBAdapter .DBAdapter interacts with the database and replies the result.
I send in the CreditCardNumber in the request and recieve its Status (VALID,INVALID). i get this error every time . i have tried almost every thing to fix this . Please help me with same .
Below is the complete error stacktrace.
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'getCreditValidationSelect' failed due to: DBReadInteractionSpec Execute Failed Exception. Query name: [getCreditValidationSelect], Descriptor name: [getCreditValidation.Creditcardinfo]. Caused by java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist . See root exception for the specific exception. This exception is considered retriable, likely due to a communication failure. To classify it as non-retriable instead add property nonRetriableErrorCodes with value "942" to your deployment descriptor (i.e. weblogic-ra.xml). To auto retry a retriable fault set these composite.xml properties for this invoke: jca.retry.interval, jca.retry.count, and jca.retry.backoff. All properties are integers. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Thanks in advance

Can you please check the following
a. check the JNDI Configuration. ( check for the value used for XADatasourceName )
b. check the Data source created for the User.
c. Incase you have updated the existing JNDI then you need to update the adapter with the New Deployment Plan.
Thanks,
Sunil Gopal

Java.sql.SQLException: ORA-00942: table or view does not exist

Hi all,
I have an Oracle table called: USER_APP_VERSION with the fields (all String): (username, application_name, version).
I use PreparedStatement to insert rows into table:
String psInsertRpt = "INSERT INTO USER_APP_VERSION (username, application_name, version) VALUES (?, ?, ?)";
rptPS = conn.prepareStatement(psInsertRpt);
rptPS.setString(1, username);
rptPS.setString(2, source);
rptPS.setString(3, version);
rptPS.executeUpdate(); At executeUpdate() line, I get the following error:
java.sql.SQLException: ORA-00942: table or view does not exist
The table does exist, I can use the "INSERT INTO USER_APP_VERSION (username, application_name, version) VALUES ("name", "source", "version")";
to insert rows into db at sql command line, however, when run the same query as part of my Java code, get the SQLException.
Any idea? Any help is greatly appreciated.

Thanks for the raply. I can connect to the db using a username and password, and run the query with no problem. I use the same username and password to make a jdbc connection from Java code. Since username and password are the same, does "permission" is still an issue? If yes, how can I solve it?

ORA-00604:error occurred at recursive SQL level1 ORA-01000:maximum open cur

Dear Experts,
I got Error During WebLoad Testing.
Please give me solution.
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-01000: maximum open cursors exceeded

It depends on how may cursors are used in your program and the parameter value for OPEN_CURSORS. If it is not possible to reduce the number cursors used in the program increase the OPEN_CURSORS value.
regards

Scheduling error causing - ORA-00942: table or view does not exist

Hello
I have the following problem, I created an scenario that its supposed to run every 1 hour, it has an interface that moves an amount of records from one table to another (the amount of records is not fixed it changes). The problem arises when the amount of data to move is so big that the hour between executions is not enough and the scenario is still running when a second execution of the same scenario starts to run (as scheduled), so in the interface when the second process is trying to run the loading step it fails and I got the error ODI-1228 Caused By: java.sql.BatchUpdateException: ORA-00942: table or view does not exists. So the scenario fails and it logs this error. I think the error is due to the table in stage being locked by the first execution of the scenario.
I don't want to change the amount of time between executions because it is usually enough, I just want to avoid the execution of a scenario when there is another execution of the same scenario still running, is there any way to do this?.
Thanks
LJ

Hello
Thanks for your answer, I already have the "Interval between repetitions" property set to 1 hour, but when one execution takes more than one hour the scheduler starts another and I have 2 processes accessing the same table and it is when I have a concurrence error on the staging table.
How can I ensure that I wont have two or more executions of the same scenario running at the same time?.
Thanks,
LJ

10gLiteR3 publishing ORA-00942: table or view does not exist error

Hi All,
I am encountering table or view does not exist error while publishing using the api.
Below is the code:
try {
consolidatorManager.openConnection("MOBILEADMIN","PASSWORD", ADMIN_JDBC_URL);
mobileResourceManager = new MobileResourceManager("MOBILEADMIN","PASSWORD",ADMIN_JDBC_URL);
consolidatorManager.createPublicationItem(EXT_CONN, "RMT_TEST_TABLE" , "MOBILEADMIN","RMT_TEST_TABLE", "F", "SELECT * FROM MOBILEADMIN.RMT_TEST_TABLE", null, null);
consolidatorManager.addPublicationItem(mobileResourceManager.getPublication("/mobileApp"),"RMT_TEST_TABLE",null, null, "S", null, null);
} catch (Exception e) {
e.printStackTrace();
When I execute the above code it does not throw any exceptions but I see the below error in err.log. I,U,D triggers are getting created on the remote table, CMP, CFM, CVR,CLG tables are also created, I also see primary key for this table in VPKS. Publishing seems to be fine but I see the below error in err.log.
java.sql.SQLException: ORA-00942: table or view does not exist
     at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:180)
     at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
     at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
     at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1451)
     at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteDescribe(TTC7Protocol.java:651)
     at oracle.jdbc.driver.OracleStatement.doExecuteQuery(OracleStatement.java:2117)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:2331)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:422)
     at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:366)
     at oracle.lite.sync.Subscription.getVirtualTablePrimaryKey(Subscription.java:7522)
     at oracle.lite.sync.Subscription.getTablePrimaryKey(Subscription.java:7365)
     at oracle.lite.sync.Subscription.CreatePublicationItem(Subscription.java:2334)
     at oracle.lite.sync.Subscription.CreatePublicationItem(Subscription.java:2157)
     at oracle.lite.sync.Subscription.CreatePublicationItem(Subscription.java:2129)
     at oracle.lite.sync.Subscription.CreatePublicationItem(Subscription.java:2108)
     at oracle.lite.sync.Subscription.CreatePublicationItem(Subscription.java:2093)
     at oracle.lite.sync.Subscription.CreatePublicationItem(Subscription.java:2079)
     at oracle.lite.sync.ConsolidatorManager.createPublicationItem(ConsolidatorManager.java:1253)
I am not able to figure out what table it is looking for. Any ideas why this is happening?

check the MGP compose process, is it also showing the error?
If it is them at some point in 10.2 Oracle introduced a 'feature' (ie: bug) that causes problems to the housekeeping routines when new versions of publication items are published
In 10.0 and early 10.2 when making changes to publication items VIEWS called CPV$.. were created to log the column list for each version of a publication item, and check if you are making changes when you publish. In the case of old versions, once all clients have synchronised and been moved to the latest version it tries to delete this view.
at some point the publish started creating TABLES instead of views (but using the same naming convention ie: CPV$..). This works fine as far as the logging of changes and old column lists, but the housekeeping called at the end of the publish and GP process still trieds to do a DROP VIEW and this causes the error.
The only way of clearing this i have found is to look at the log file to get the name of the object that it is trying to drop, set up a view script to create a dummy view with the list of columns in the table, drop the table and then create the view. It then gets dropped on the next MGP cycle and the error goes away
If the error is not showing up in the MGP process, only in the publish, and your changes appear to be publishing OK, then the problem is likely to be with a snapshot definition AFTER the change you have made - real pain to identify on re-publish - possibly missing schema name in the snapshot definition

ORA-00942: table or view does not exist show in defaultTrace. n .trc

When i checked my portal backend trace file today, i saw lots of below error trace:
#1.5 #0003BA78185F00400000004400001DE90004464D1AF14829#1203196885279#com.sap.sql.jdbc.direct.DirectPreparedStatement#sap.com/irj#com.sap.sql.jdbc.direct.DirectPreparedStatement#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Database/sql/jdbc/direct#Java#com.sap.sql_0003##SQL error occurred on connection epprd:EPP:SAPSR3DB: code=942, state="42000", message="ORA-00942: table or view does not exist
SQL statement is "INSERT INTO "SAPEPPDB"."NAV_HASHEDURLS" ("HASHEDVALUE","URL") VALUES (?,?)".
[EXCEPTION]
#6#942#42000#ORA-00942: table or view does not exist
#epprd:EPP:SAPSR3DB#INSERT INTO "SAPEPPDB"."NAV_HASHEDURLS" ("HASHEDVALUE","URL") VALUES (?,?)#java.sql.SQLException: ORA-00942: table or view does not exist
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3315)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3399)
     at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPreparedStatement.java:103)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:325)
     at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:252)
     at com.sapportals.portal.navigation.HashingServicesDBHandler.insertHashedValue(HashingServicesDBHandler.java:258)
     at com.sapportals.portal.navigation.HashingServices._addHashedValueToDB(HashingServices.java:242)
     at com.sapportals.portal.navigation.HashingServices.getHashedValue(HashingServices.java:77)
     at com.sapportals.portal.navigation.NavigationService.getNavigationNodeHashedName(NavigationService.java:1814)
     at com.sapportals.portal.navigation.NavigationNode.getHashedName(NavigationNode.java:347)
     at com.sapportals.portal.navigation.DetailedNavigationTree.addNavigationNodeToTree(DetailedNavigationTree.java:926)
     at com.sapportals.portal.navigation.DetailedNavigationTree.addNavigationNodesToTree(DetailedNavigationTree.java:909)
     at com.sapportals.portal.navigation.DetailedNavigationTree.addNavNodeChildrenToTree(DetailedNavigationTree.java:863)
     at com.sapportals.portal.navigation.DetailedNavigationTree.doOnNodeReady(DetailedNavigationTree.java:369)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:177)
     at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:410)
     at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:233)
     at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:635)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)
     at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:815)
     at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:703)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #0003BA78185F00400000004500001DE90004464D1AF14ECE#1203196885290#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###java.sql.SQLException: ORA-00942: table or view does not exist
#1.5 #0003BA78185F00400000004600001DE90004464D1AF15015#1203196885290#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)#
#1.5 #0003BA78185F00400000004700001DE90004464D1AF15123#1203196885291#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)#
#1.5 #0003BA78185F00400000004800001DE90004464D1AF15225#1203196885291#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)#
#1.5 #0003BA78185F00400000004900001DE90004464D1AF153BD#1203196885291#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)#
#1.5 #0003BA78185F00400000004A00001DE90004464D1AF154C8#1203196885292#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)#
#1.5 #0003BA78185F00400000004B00001DE90004464D1AF155D2#1203196885292#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)#
#1.5 #0003BA78185F00400000004C00001DE90004464D1AF156DC#1203196885292#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)#
#1.5 #0003BA78185F00400000004D00001DE90004464D1AF157E5#1203196885293#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3315)#
#1.5 #0003BA78185F00400000004E00001DE90004464D1AF1590A#1203196885293#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3399)#
#1.5 #0003BA78185F00400000004F00001DE90004464D1AF15A0F#1203196885293#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeUpdate(BasicPreparedStatement.java:103)#
#1.5 #0003BA78185F00400000005000001DE90004464D1AF15B33#1203196885293#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeUpdate(DirectPreparedStatement.java:325)#
#1.5 #0003BA78185F00400000005100001DE90004464D1AF15C3C#1203196885294#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.sql.jdbc.common.CommonPreparedStatement.executeUpdate(CommonPreparedStatement.java:252)#
#1.5 #0003BA78185F00400000005200001DE90004464D1AF15D46#1203196885294#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.HashingServicesDBHandler.insertHashedValue(HashingServicesDBHandler.java:258)#
#1.5 #0003BA78185F00400000005300001DE90004464D1AF15E4F#1203196885294#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.HashingServices._addHashedValueToDB(HashingServices.java:242)#
#1.5 #0003BA78185F00400000005400001DE90004464D1AF15F55#1203196885294#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.HashingServices.getHashedValue(HashingServices.java:77)#
#1.5 #0003BA78185F00400000005500001DE90004464D1AF1605C#1203196885295#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.NavigationService.getNavigationNodeHashedName(NavigationService.java:1814)#
#1.5 #0003BA78185F00400000005600001DE90004464D1AF16167#1203196885295#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.NavigationNode.getHashedName(NavigationNode.java:347)#
#1.5 #0003BA78185F00400000005700001DE90004464D1AF16275#1203196885295#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.DetailedNavigationTree.addNavigationNodeToTree(DetailedNavigationTree.java:926)#
#1.5 #0003BA78185F00400000005800001DE90004464D1AF16381#1203196885295#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.DetailedNavigationTree.addNavigationNodesToTree(DetailedNavigationTree.java:909)#
#1.5 #0003BA78185F00400000005900001DE90004464D1AF1648E#1203196885296#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.DetailedNavigationTree.addNavNodeChildrenToTree(DetailedNavigationTree.java:863)#
#1.5 #0003BA78185F00400000005A00001DE90004464D1AF16597#1203196885296#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.navigation.DetailedNavigationTree.doOnNodeReady(DetailedNavigationTree.java:369)#
#1.5 #0003BA78185F00400000005B00001DE90004464D1AF1669E#1203196885296#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)#
#1.5 #0003BA78185F00400000005C00001DE90004464D1AF167A7#1203196885297#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)#
#1.5 #0003BA78185F00400000005D00001DE90004464D1AF168AB#1203196885297#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)#
#1.5 #0003BA78185F00400000005E00001DE90004464D1AF169AF#1203196885297#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)#
#1.5 #0003BA78185F00400000005F00001DE90004464D1AF16AB3#1203196885297#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.pb.PageBuilder.createAndAddEmbeddediView(PageBuilder.java:177)#
#1.5 #0003BA78185F00400000006000001DE90004464D1AF16BB8#1203196885298#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.pb.PageBuilder.createiView(PageBuilder.java:410)#
#1.5 #0003BA78185F00400000006100001DE90004464D1AF16CBB#1203196885298#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.pb.PageBuilder.createAndAddiViews(PageBuilder.java:233)#
#1.5 #0003BA78185F00400000006200001DE90004464D1AF16E30#1203196885298#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.pb.PageBuilder.doOnNodeReady(PageBuilder.java:635)#
#1.5 #0003BA78185F00400000006300001DE90004464D1AF16F39#1203196885298#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:388)#
#1.5 #0003BA78185F00400000006400001DE90004464D1AF17043#1203196885299#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.pb.PageBuilder.handleEvent(PageBuilder.java:815)#
#1.5 #0003BA78185F00400000006500001DE90004464D1AF17148#1203196885299#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.component.CachablePortalComponent.handleEvent(CachablePortalComponent.java:703)#
#1.5 #0003BA78185F00400000006600001DE90004464D1AF1724F#1203196885299#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)#
#1.5 #0003BA78185F00400000006700001DE90004464D1AF173B2#1203196885300#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)#
#1.5 #0003BA78185F00400000006800001DE90004464D1AF1762B#1203196885300#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:340)#
#1.5 #0003BA78185F00400000006900001DE90004464D1AF17754#1203196885301#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:642)#
#1.5 #0003BA78185F00400000006A00001DE90004464D1AF17868#1203196885301#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)#
#1.5 #0003BA78185F00400000006B00001DE90004464D1AF17976#1203196885301#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)#
#1.5 #0003BA78185F00400000006C00001DE90004464D1AF17A78#1203196885301#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0003BA78185F00400000006D00001DE90004464D1AF17B7D#1203196885302#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)#
#1.5 #0003BA78185F00400000006E00001DE90004464D1AF17C81#1203196885302#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5 #0003BA78185F00400000006F00001DE90004464D1AF17D85#1203196885302#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#
#1.5 #0003BA78185F00400000007000001DE90004464D1AF17E8F#1203196885302#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#
#1.5 #0003BA78185F00400000007100001DE90004464D1AF17F92#1203196885303#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)#
#1.5 #0003BA78185F00400000007200001DE90004464D1AF1809A#1203196885303#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)#
#1.5 #0003BA78185F00400000007300001DE90004464D1AF181A4#1203196885303#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)#
#1.5 #0003BA78185F00400000007400001DE90004464D1AF182AD#1203196885303#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)#
#1.5 #0003BA78185F00400000007500001DE90004464D1AF183B3#1203196885304#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)#
#1.5 #0003BA78185F00400000007600001DE90004464D1AF184BB#1203196885304#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)#
#1.5 #0003BA78185F00400000007700001DE90004464D1AF185C1#1203196885304#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)#
#1.5 #0003BA78185F00400000007800001DE90004464D1AF186C6#1203196885305#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)#
#1.5 #0003BA78185F00400000007900001DE90004464D1AF187CE#1203196885305#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#
#1.5 #0003BA78185F00400000007A00001DE90004464D1AF188DE#1203196885305#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#
#1.5 #0003BA78185F00400000007B00001DE90004464D1AF18AAC#1203196885305#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
#1.5 #0003BA78185F00400000007C00001DE90004464D1AF18BB4#1203196885306#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at java.security.AccessController.doPrivileged(Native Method)#
#1.5 #0003BA78185F00400000007D00001DE90004464D1AF18CB7#1203196885306#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)#
#1.5 #0003BA78185F00400000007E00001DE90004464D1AF18DBB#1203196885306#System.err#sap.com/irj#System.err#PETER#42062##epprd_EPP_6267450#PETER#20a289a0dcd511dca39f0003ba78185f#SAPEngine_Application_Thread[impl:3]_39##0#0#Error##Plain###     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)#
It seems system try to insert record into table NAV_HASHEDURLS, this table belong to scheme SAPSR3DB, not SAPEPPDB, i don't know why this happens, any experts know how to change it and where it come from. I have another EP, don't have above error.
Thanks

This is a bug, see note Note 1140239 - Navigation short Urls aren't seen in short urls monitor

Backup report function returns: ORA-00942: table or view does not exist

Hello All,
I recently switched over from control file RMAN to recovery catalog. I logged into the 11g database control, executed a full backup and all went well. However, I just noticed that after I click on 'Backup Report' in database control (enterprise manager) I get the following error message: " java.sql.SQLException: ORA-00942: table or view does not exist"
I was able to view backup reports prior to switching over to recover catalog. What am I missing or what is missing, sort to speak?
Thanks all !
-Ron

Thanks for the reply Werner. I did try it as 'SYS' but no luck. Strange...This was a new enterprise manager - DB control and the backup reprt function was working prior to using the recover catalog. Anthing in the recovery catalog database that may be missing?
Rob..

Cannot insert PS_TXN ORA-00942 table or view does not exist

We are using jdev 11.1.1.4.0
We have two users in the database and various application modules which connect to these users using datasources
We have tested the application with applicatin module pooling enabled off to test for passivation and activation errors and the application works fine.
Also on our internal test enviorment which has more then 10 concurrent users the application works fine
But at UAT it has started suddenly to give errors Cannot insert in PS_TXN ORA-00942 table or view does not exist
When I see the data in PS_TXN tables in various users I can see that passivation has taken place for the same day when there sporadic errors have been reported all having the cause as ORA-00942 table or view does not exist.
But one strange thing that I have observed is that the COLLID column has sequence numbers interchanged for the users randomly, database user 1 has sequence number from database user 2 seq and vice a versa in COLLID
As far as this problem goes the passivation should have failed with ORA-00001 primary key voilated but that is not the case
May be the keys have still not got to a number where they collide.
But I am totally taken aback on such a behaviour and I am not sure how to correct it.
So we have two porblems here
1) why did this error come in first place PS_TXN ORA-00942 table or view does not exist
2) Why are the sequence numbers interchanged for the databse users ?
Edited by: user3067156 on Jun 19, 2012 3:12 AM

I got reply to my second question
It looks like a bug in the framework and the suggestions are to use only one ps_txn and ps_txn_seq by modifying the internal connection
But the first problem is not yet known why did it appear suddenly
Edited by: user3067156 on Jun 19, 2012 3:12 AM

Select dba_users - ORA-00942: table or view does not exist

Hi,
I need to access dba_users to show some information on a report but could not access from apex it show every time
failed to parse SQL query:
ORA-00942: table or view does not exist
The problem is only on apex I could access from sqlplus or others tools.
Thanks

Hi Scott, Rafael and Ben,
I assume this then means that the parsing schema needs objects to be granted directly rather than through a role, the same as if you are parsing object references in pl/sql.
Rafael, there is a view called all_users to which you have access, but it provides much less information.
Andre

SQL Error: ORA-00942: table or view does not exist + CX_RS_SQL_ERROR

HI ,
we are facing below issue while activating info object xxxxxxxx
" SQL Error: ORA-00942: table or view does not exist " and " CX_RS_SQL_ERROR "
can any one help us out to resolve this issue.
Thanks,
EDK......

Hi,
Check the corrections given in the note 990764:
Reason and Prerequisites
Up to now, using a characteristic with its own master data read class as the InfoProvider was not supported. This is now released but it is not available for all modelings. Using the attributes in the query is not supported for characteristics that have their own master data read class. Using the attributes in the query causes a termination. The following errors may occur in this case:
ORA-00942: table or view does not exist
Fehler in CL_SQL_RESULT_SET Include NEXT_PACKAGE
RAISE_READ_ERROR in CL_RSDRV_VPROV_BASE
Solution
SAP NetWeaver 2004s BI
Import Support Package 11 for SAP NetWeaver 2004s BI (BI Patch 11 or SAPKW70011) into your BI system. The Support Package is available once Note 0914305 "SAPBINews BI 7.0 Support Package 11", which describes this Support Package in more detail, has been released for customers.
In urgent cases you can implement the correction instructions.
The correction instructions contain the tightened inspection for characteristics.
Regards,
Anil Kumar Sharma .P

Error(20,22): PL/SQL: ORA-00942: table or view does not exist

I am getting currently getting an error when I try and insert into a table from a different schema from my Stored Procedure:
Error(20,22): PL/SQL: ORA-00942: table or view does not exist
I am explicitly calling the table with the schema name infront i.e.
INSERT INTO SAPSR3.ZTREC_NAME_TYPE
MASTER_ID,
NAME_TYPE,
FAMILY_NAME,
FIRST_NAME,
MIDDLE_NAME,
TITLE
VALUES
In_MasterID,
In_NameType,
In_FamilyName,
In_FirstName,
In_MiddleName,
In_Title
I only get this error when I try and compile my stored procedure. If I try this insert not within a stored procedure (i.e. a blank script) it works perfectly.
Can anyone tell me what Im doing wrong?
Thanks.

Hi,
It sounds like you (the procedure owner) have privileges on that table only through a role.
Roles don't count in stored procedures created with AUTHID OWNER (which is the default).
Either
(1) Have user SAPSR3 grant the necessary privileges directly to you (or to PUBLIC), or
(2) change the procedure so that it runs with the caller's privileges, by adding AUTHID CURRENT_USER after the argument list but before the keyword IS (os AS) like this:
CREATE OR REPLACE PROCEDURE foo
( x IN NUMBER
AUTHID CURRENT_USER
IS ...

Process chain failure SQL ERROR 942 ORA-00942:table or view does not exist

HI all,
We have a proces chain with 'ceate index' process type and got failed with an error as follows......
SQL ERROR 942 ORA-00942:table or view does not exist
Plz can anyone give solution for this error.
SATISH.

Hey Satish,
Please refer to this thread:
BRCONNECT fails with SQL error -942 at location ora_vers_get-1
I am sure the solution there should solve your problem. There are various other discussions about this error in the forum, I suggest you look through them for better understanding and additional material.
Cheers!!!
Manu.

PL/SQL: ORA-00942: table or view does not exist

Hi
i have logged into my schema and trying to access the database "DAD" which has the table name "SCHOOL"
i wrote a function which should give me new_sno when i give it the old_sno
and i have this errors , pls help
CREATE OR REPLACE FUNCTION ORIG_SN(OSNO in Number,OTN in Number)
RETURN Number IS
NEW_SNO Number:=0;
BEGIN
SELECT new_sno AS NEW_SNO
FROM DAD.SCHOOL
WHERE ORIG_SNO = OSNO AND ORIG_TN = OTN;
RETURN NEW_SNO;
END ORIG_SN;
Warning: Function created with compilation errors.
Errors for FUNCTION ORIG_SN:
LINE/COL ERROR
5/1 PL/SQL: SQL Statement ignored
6/15 PL/SQL: ORA-00942: table or view does not exist
Thanks in advance ..

Try this,
CREATE VIEW SCHOOL_VIEW AS SELECT * FROM DAD.SCHOOL;and then change your function like
CREATE OR REPLACE FUNCTION ORIG_SN(OSNO in Number,OTN in Number)
RETURN Number IS
my_new_sno Number:=0;
BEGIN
SELECT new_sno INTO my_new_sno FROM SCHOOL_VIEW WHERE ORIG_SNO = OSNO AND ORIG_TN = OTN;
RETURN my_new_sno;
END ORIG_SN;and see if it is getting created without any errors.
-Arun
Edited by: Arunkumar Ramamoorthy on Aug 15, 2009 1:56 AM

ERROR ORA-00942: table or view does not exist

Hi:
I created a .sql file and a loader file. Running the .sql file with sql * plus Worksheet:
declare
gr sdo_georaster;
begin
select image into gr from gis.RasterImages where geoid=1 for update;
sdo_geor.generatePyramid(gr,'resampling=NN');
update gis.RasterImages set image=gr where geoid=1;
commit;
end;
I trying to create a pyramid,but the error appeared:
ERROR at line 1:
ORA-29400: DATA CONTROL ERROR ORA-00942: table or view does not exist
ORA-06512: 在 "MDSYS.SDO_GEOR_INT", line 162
ORA-06512: 在 "MDSYS.SDO_GEOR", line 826
ORA-06512: 在 line 5
I don't know why?
Anyone can help me?
Thanks.

Hi,
I think you are executing the select statement for schema X and the table is in the schema srnr.
And schema X is not having select privilege on the table 'students' present in schema srnr.
Goto schema srnr.
Execute the following statement:
grant select on students to X;
This will give schema X the privilege to query the table students present in srnr.
Regards,
Anupama

ERROR OCCURED AT RECURSIVE SQL LEVEL1 ORA-00942:TABLE OR VIEW DOSEN'T EXIST

Similar Messages

Maybe you are looking for