Oracle Error 1003
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members exp-00008: oracle error 904 encountered Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To exp-00008 oracle error 904 encountered ora-00904 invalid identifier YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Oracle: Oracle release - 9i and earlier Forum at Tek-Tips HomeForumsProgrammersDBMS PackagesOracle: Oracle release - 9i and earlier Forum ORA-01003: no statement parsed thread759-469294 Forum Search FAQs Links MVPs ORA-01003: no statement parsed ORA-01003: no statement parsed ratfink (IS/IT--Management) (OP) 7 Feb 03 08:47 I have an 8.1.6 database patched to a 8.1.6.3.8. The database seems happy while it is running, but when I do an exp I get two errorsEXP-00008: ORACLE error 1003 encounteredORA-01003: no statement parsedEXP-00008: ORACLE error 904 encounteredORA-00904: invalid column namePlease help! RE: ORA-01003: no statement parsed karluk (MIS) 7 Feb 03 13:32 According to Metalink note 106155.1, this type of error is most likely caused by a version mismatch between the database and the export utility.Perhaps installing the 8.1.6.3.8 patch created the mismatch.The suggested fix is to rerun catalog.sql and catproc.sql as sys.That, among other things, will recreate your export views.There appear to be other causes of this error.The Metalink note says that a large export that exceeds your file size limit can also create this type of error. Red Flag This Post Pleas
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in General Database Discussions All PlacesDatabaseGeneral Database Discussions This discussion is archived 7 Replies Latest reply on Jun 25, 2011 7:20 AM by user13461835 error while using exp utility 684379 Apr 2, 2009 7:23 AM Hi, I am getting the following oracle error while using exp, can someone please suggest on this, About to export specified http://www.tek-tips.com/viewthread.cfm?qid=469294 users ... . exporting pre-schema procedural objects and actions . exporting foreign function library names for user SIEBEL . exporting PUBLIC type synonyms . exporting private type synonyms . exporting object type definitions for user SIEBEL About to export SIEBEL's objects ... . exporting database links . exporting sequence numbers . exporting cluster definitions . about to export SIEBEL's tables via Conventional Path ... . . exporting https://community.oracle.com/thread/882259 table EIM_ACCDTL_TNT EXP-00008: ORACLE error 904 encountered ORA-00904: "MAXSIZE": invalid identifier . . exporting table EIM_ACCNTROUTE EXP-00008: ORACLE error 1003 encountered ORA-01003: no statement parsed . . exporting table EIM_ACCNT_CUT EXP-00008: ORACLE error 904 encountered ORA-00904: "MAXSIZE": invalid identifier . . exporting table EIM_ACCNT_DTL EXP-00008: ORACLE error 1003 encountered ORA-01003: no statement parsed I have the same question Show 0 Likes(0) 8719Views Tags: none (add) This content has been marked as final. Show 7 replies 1. Re: error while using exp utility Satish Kandi Apr 2, 2009 7:24 AM (in response to 684379) Few more details about the client and server Oracle versions and OS would be helpful. Like Show 0 Likes(0) Actions 2. Re: error while using exp utility zaffer khan, cisa Apr 2, 2009 7:52 AM (in response to 684379) ORA-02494: invalid or missing maximum file size in MAXSIZE clause Cause: UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value. Action: Use correct syntax. Like Show 0 Likes(0) Actions 3. Re: error while using exp utility 684379 Apr 2, 2009 8:01 AM (in response to Satish Kandi)
6.3 Troubleshooting GuidePrevious: ChapterĀ 9 Directory Server Error Log Message ReferenceCommon Error Codes This section describes the error codes displayed in the instance-path/logs/errors log and the appropriate action to take should these errors occur. 1000: Server startup Description: Proxy https://docs.oracle.com/cd/E19316-01/820-2768/dps-common-error-codes/index.html instance has started. Solution: dpadm start 1001: Clean Server Shutdown Description: Clean Server Shutdown alert is displayed when the Directory Proxy Server instance is stopped via. LDAP by the ShutDown task plug-in. The command-line interface http://stackoverflow.com/questions/12252792/why-im-getting-the-ora-01003-no-statement-parsed-error implementation does not currently use this stop method. Solution: An RFE (CR 6628583) has been filed to either change the way the dpadm command shuts down the server. 1002: Abrupt Server Shutdown Description: Directory Proxy oracle error Server instance has shut down abruptly. Cause: Proxy was stopped through the command-line utility or Proxy JVM exited (Unexpected Fatal Exception, Out Of Memory...) Solution: Restart the Directory Proxy Server instance. dpadm restart 1003: Configuration Reloaded: OK Description: This alert is raised when the proxy dynamically reload the configuration file as a whole. This may happen in the following scenarios: The Reload Configuration task plug-in is invoked via LDAP. This oracle error 904 is currently not used by the monitoring framework. It is possible to configure the proxy to automatically reload its configuration file when it is manually modified, that is, using a text editor. This feature is disabled by default for security and reliability reasons. This alert is never raised using standard configuration. Cause: The configuration file is changed on the disk. Solution: Do not manually edit the configuration file, use dpconf to configure the proxy instance. Modify the config.ldif file with a text editor and save to the disk. 1004: Configuration Reloaded: Warning Description: See the error code 1003. The server failed to reload the configuration but the running instance is not impacted by the configuration problem. As for the error code 1003, this can never occur with a default configuration as automatic configuration reloading is disabled. 1005: Configuration Reloaded: Error Description: See the error code 1003. The server failed to reload the configuration and the running instance could possibly be impacted by the configuration problem. As for the error code 1003, this can never occur with a default configuration as automatic configuration reloading is disabled. 2000: Data Source Not Available Description: A data Source is not available anymore. Last proactive monitoring query showed data source is unavailable. C
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Why I'm getting the ORA-01003: no statement parsed error? up vote 1 down vote favorite Why am I getting this error and what does it mean by no statement parsed. ORA-01003: no statement parsed Here is the code: PROCEDURE ORIGINAL_TABLE.UPDATE_GROUPS IS -- cursor loaded with the swam groups CURSOR cursor1 IS SELECT ID, NEW_DESCRIPTION FROM NEW_TABLE.NEW_GROUP_TABLE@DB_LINK.X; BEGIN FOR C1_REC IN cursor1 LOOP UPDATE ORIGINAL_TABLE."GROUPS" SET GROUP_ID = C1_REC.ID WHERE ORIGINAL_TABLE."GROUPS".DESCRIPTION = C1_REC.NEW_DESCRIPTION; IF (SQL%ROWCOUNT = 0) THEN INSERT INTO ORIGINAL_TABLE.GROUPS("GROUP_ID", "DESCRIPTION") VALUES (C1_REC.ID, C1_REC.NEW_DESCRIPTION); END IF; END LOOP; EXCEPTION WHEN OTHERS THEN dbms_output.put_line(SQLERRM); END; What I try to do with the code above is to update and old table with the values from a new table and in case that the new group doesn't exist insert it. Update: Changed %ROWCOUNT > 0 for %ROWCOUNT = 0 oracle stored-procedures plsql share|improve this question edited Sep 3 '12 at 19:22 asked Sep 3 '12 at 18:53 M.Octavio 5141723 1 Have you tested cursor query in another window? I think it because of query –HRgiger Sep 3 '12 at 19:08 Is this when you compile the procedure or when you execute it? Do you get a line? Maybe you need to remove the exception for a test. What also confuses me is why do you do the insert when SQL%ROWCOUNTis > 0 shouldn't that be = 0? But that is not your problem. And yes, does the select work as a single statement? –hol Sep 3 '12 at 19:17 yes the select works as a single statement, it happens when I execute the procedure. It compile without errors. –M.Octavio Sep 3 '12 at 19:19 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted Use MERGE statement, it does update/insert stuff more efficiently and pay attention your plsql doesn't provide it is intended for. It tries to make an update statement and if a record found it inserts another record. In order to fix it use IF (SQL%ROWCOUNT = 0) I presume the reason of the issue is the . in DBLINK name. Moreover I would suggest to get rid of quotes f