Skip to main content

ORA-02289 SEQUENCE DOES NOT EXIST


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Note: here we are trying to insert  values in a table from another user Which has access.

SQL Error: ORA-02289: sequence does not exist
02289. 00000 - "sequence does not exist"
*Cause: The specified sequence does not exist, or the user does
           not have the required privilege to perform this operation.
*Action: Make sure the sequence name is correct, and that you have
           the right to perform the desired operation on this sequence.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

generating query is not having SCHEMA NAME suffixed before the SEQUENCE NAME. Please see below example’s for easy understanding.

Please see painted values in the below queries.

SQL> show user;
USER is "RKPYTE"

FAILING SQL:

SQL> insert into RKPYTE.TRANSACTION_IMPORT(TRANSACTION_IMPORT_ID,IMPORT_RUN_CODE,SOURCE_TRANSACTION_ID,DELIVERY_METHOD_CODE,TRANSACTION_DATE,PATRON_ACCOUNT_ID) values(TRANSACTION_IMPORT_ID_SEQ.nextval,'DEC31','6788','MAIL',sysdate,'164063');
insert into RKPYTE.TRANSACTION_IMPORT(TRANSACTION_IMPORT_ID,IMPORT_RUN_CODE,SOURCE_TRANSACTION_ID,DELIVERY_METHOD_CODE,TRANSACTION_DATE,PATRON_ACCOUNT_ID) values(TRANSACTION_IMPORT_ID_SEQ.nextval,'DEC31','6788','MAIL',sysdate,'164063')
                                                                                                                                                                   *
ERROR at line 1:
ORA-02289: sequence does not exist

RIGHT SQL:

SQL> insert into RKPYTE.TRANSACTION_IMPORT(TRANSACTION_IMPORT_ID,IMPORT_RUN_CODE,SOURCE_TRANSACTION_ID,DELIVERY_METHOD_CODE,TRANSACTION_DATE,PATRON_ACCOUNT_ID) values(RKPYTE.TRANSACTION_IMPORT_ID_SEQ.nextval,'DEC31','6788','MAIL',sysdate,'164063');

1 row created.

Thank You!!


Comments

Popular posts from this blog

Registering The Database to RMAN catalog database:

Registering The Database to RMAN catalog database: Need to start RMAN as follows: RMAN target=sys/password@database_to_backup rcvcat=sys/password@recovery_catalog_database Another variation on the command, if the recovery catalog and the database were on the same server, might be as shown: oraenv ORACLE_SID = [KKUY] ? KKUY RMAN rcvcat=sys/password@recovery_catalog_database RMAN> connect target Recovery Manager: Release 8.0.5.1.0 - Production RMAN-06005: connected to target database: KKUY RMAN-06008: connected to recovery catalog database Use the below command to register the database. RMAN>register database; Want to verify if a database is registered in the recovery catalog. To do this, connect to RMAN and issue the command LIST INCARNATION OF DATABASE. RMAN> list incarnation of database; RMAN-03022: compiling command: list RMAN-06240: List of Database Incarnations RMAN-06241: DB Key Inc Key DB Name DB ID      CUR Reset SCN   Reset Time RMAN

ORA-39014: One or more workers have prematurely exited.ORA-00018: maximum number of sessions exceeded

ERROR: I was Performing a full database import and during the import I faced the below error. ORA-39014: One or more workers have prematurely exited. ORA-39029: worker 6 with process name "DW07" prematurely terminated ORA-31672: Worker process DW07 died unexpectedly. Job "SYSTEM"."SYS_IMPORT_FULL_04" stopped due to fatal error at 00:59:40 ORA-39014: One or more workers have prematurely exited. SOLUTION:  Run the import with fewer parallel processes, like PARALLEL=2 instead of 8. I was able to run the import successfully. NOTE 1: This errors occurs when there are less session allocation in the database. check the session,process parameters and increase them accordingly. To avoid such errors again. NOTE 2 : Note: Increasing processes parameter increases the amount of shared memory that needs to be reserved & the OS must be configured to support the larger amount of shared memory. So here we first need to increase the Memory & SG