Ora 20001 ошибка oracle

[{«Product»:{«code»:»SS9S6B»,»label»:»IBM Cognos Controller»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Component»:»Controller»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»8.3″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

I’m trying to create a library system (school work) using oracle 10g but i got stuck in creating the simple APEX report and form, the error message says:

ORA-20001: Unable to create modules. ORA-20001: Create pages error.
ORA-20001: Unable to create form page. ORA-20001: Error page=8
item=»P8_BRANCHID» id=»» ORA-20001: Error page=8 item=»P8_BRANCHID»
id=»» has same name as existing application-level item. ORA-0000:
normal, successful completion

Unable to create application.

This is my schema, in case I did something wrong:

create table publisher(
PublisherName varchar2(30) not null,
Address varchar2(30) not null,
Phone number(20),
constraint publisher_pk primary key (PublisherName)
);

create table book(
BookId number(4) not null,
Title varchar2(50) not null,
PublisherName varchar2(30) not null,
constraint book_pk primary key (BookId),
constraint book_fk foreign key (PublisherName)
references publisher (PublisherName)
);

create table bookauthors(
BookId number(4) not null,
AuthorName varchar2(30) not null,
constraint bookauthors_pk primary key (BookId,AuthorName),
constraint bookauthors_fk foreign key (BookId) references book (BookId)
);

create table librarybranch(
BranchId number(4) not null,
BranchName varchar2(30) not null,
Address varchar2(30) not null,
constraint librarybranch_pk primary key (BranchId)
);

create table borrower(
CardNo number(4) not null,
BName varchar2(30) not null, 
Address varchar2(30) not null,
Phone number(20) not null,
constraint borrower_pk primary key (CardNo)
);

create table bookcopies(
BookId number(4) not null,
BranchId number(4) not null,
No_Of_Copies number(4) not null,
constraint bookcopies_pk primary key (BookId,BranchId),
constraint bookcopies_fk foreign key (BookId) references book (BookId),
constraint bookcopies2_fk foreign key (BranchId) references librarybranch (BranchId)
);

create table bookloans(
BookId number(4) not null,
BranchId number(4) not null,
CardNo number(4) not null,
DateOut date,
DueDate date,
constraint bookloans_pk primary key (BookId,BranchId,CardNo),
constraint bookloans_fk foreign key (BookId) references book (BookId),
constraint bookloans2_fk foreign key (BranchId) references librarybranch (BranchId),
constraint bookloans3_fk foreign key (CardNo) references borrower (CardNo)
);

Thanks.

While 12.2 database is being started by srvctl, the alert log shows following messages,

Unable to obtain current patch information due to error: 20001, ORA-20001: Latest xml inventory is not loaded into table
ORA-06512: at «SYS.DBMS_QOPATCH», line 777
ORA-06512: at «SYS.DBMS_QOPATCH», line 864
ORA-06512: at «SYS.DBMS_QOPATCH», line 2222
ORA-06512: at «SYS.DBMS_QOPATCH», line 740
ORA-06512: at «SYS.DBMS_QOPATCH», line 2247
===========================================================
Dumping current patch information
===========================================================
Unable to obtain current patch information due to error: 20001
===========================================================

DBMS_QOPATCH is introduced by 12.1 database as a cool new feature ‘Queryable OPatch’. It is implemented with a PL/SQL package (DBMS_QOPATCH) and a set of tables and directories. In order to understand what the errors really are, let’s do some details research,

It should be a good guess to start from looking into the log file qopatch_log.log which modification time is very close to the time when errors was reported in alert log,

The database starting got ORA-20001 while accessing external table OPATCH_XML_INV which has
preprocessor command ‘$ORACLE_HOME/QOpatch/qopiprep.bat’. The table definition is,

File ‘qopatch_log.log’ is defined as log file of the external table, and will be generated by external table utility while table ‘OPATCH_XML_INV’ is accessed.

According to the table’s definition, PREPROCESSOR-specified command (script file) ‘qopiprep.bat’ will convert ‘raw’ data to records of the table before the table is accessible. That’s why execution error of script ‘qopiprep.bat’ is found in log ‘qopatch_log.log’. The log shows file ‘stout_orcl.txt’ cannot be created while line 55 of the script is being executed, the script code looks as following,

 54 rm -rf $ORABASE/rdbms/log/xml_file_$DBSID.xml
 55 $ORACLE_HOME/OPatch/opatch lsinventory -xml  $ORABASE/rdbms/log/xml_file_$DBSID.xml
    -retry 0 -invPtrLoc $ORACLE_HOME/oraInst.loc >> $ORABASE/rdbms/log/stout_$DBSID.txt
 56 cat $ORABASE/rdbms/log/xml_file_$DBSID.xml | sed ‘s/^ *//’ | tr ‘n’ ‘ ‘
 57 echo «UIJSVTBOEIZBEFFQBL»
 58 rm $ORABASE/rdbms/log/xml_file_$DBSID.xml
 59 rm $ORABASE/rdbms/log/stout_$DBSID.txt

Check the log directory $ORABASE/rdbms/log (here $ORABASE is same as $ORACLE_HOME) permission,

The database home owner ‘oracle’ is also the owner of the log directory, and both ‘sqlplus’ and’srvctl’ are executed by ‘oracle’ to start database, all read/write privilges should be inherited from user ‘oracle’ who has full control on the log directory. However, it is only true for sqlplus but not for srvctl.

IS srvctl accessing the external table as user other than oracle? Try to prove it by adding touch command to the script,

 54 rm -rf $ORABASE/rdbms/log/xml_file_$DBSID.xml
 55 touch /tmp/stout_$DBSID.test
 56 $ORACLE_HOME/OPatch/opatch lsinventory -xml  $ORABASE/rdbms/log/xml_file_$DBSID.xml -retry 0 -invPtrLoc $ORACLE_HOME/oraInst.loc >> $ORABASE/rdbms/log/stout_$DBSID.txt
 57 cat $ORABASE/rdbms/log/xml_file_$DBSID.xml | sed ‘s/^ *//’ | tr ‘n’ ‘ ‘
 58 echo «UIJSVTBOEIZBEFFQBL»

Try to start database with sqlplus and srvctl respectively,

See, the external table (running script qopiprep.bat) is accessed as grid while srvctl is run, but oracle while sqlplus. Here, grid is the owner of standalone Grid Infrastructure (Oracle Restart) home. What if the external table is accessed directely from sqlplus?

Apparently, it succeeded when logged onto database locally (bypass listener), and failed while remotely (going through listener. And the listener is running out of Oracle Restart home whose owner
is grid,

[oracle@host01]$ ps -ef | grep tnslsnr
    grid  1887     1   0   Jan 11 ?          19:54 /u01/app/12.2.0/grid/bin/tnslsnr LISTENER -no_crs_notify -inherit
  oracle 64664 36089   0 20:56:12 pts/3       0:00 grep tnslsnr

Although it, sometimes, made sense in previous version (10g? 11g?), it does not happen in 12.1. Therefore, it should be treated as bug :(.

As a temporary workaround, write permission can be granted to group of the log directory as grid is member of oinstall,

Payroll Reconciliation Summary, Errors: ORA-20001: Dynamic SQL for DB item failed : ORA-20001: Database item requires context TAX_UNIT_ID to be set (Doc ID 2208930.1)

Last updated on OCTOBER 01, 2020

Applies to:

Symptoms

On Production: 12.1.3 version, Australian Payroll

When attempting to Run Payroll Reconciliation Summary , the following error occurs.

Steps to Reproduce:
The issue can be reproduced at will with the following steps:

1. Login to XX Payroll Manager and navigate to View > Submit Request
2. Submit the Payroll Rec Summary Report
3. Navigate to view > assignment process results and an error occurs

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

ORA-20001, ORA-06512 Error When Reconsider Application for an Employee Applicant who has a Future Dated Termination (Doc ID 1315340.1)

Last updated on DECEMBER 09, 2022

Applies to:

Symptoms

When attempting to reverse terminate an application for an employee applicant who has a future dated termination, the following error occurs:

Exception Details.
oracle.apps.fnd.framework.OAException: java.sql.SQLException: ORA-20001:
ORA-06512: at «APPS.HR_ASSIGNMENT_API», line 607
ORA-06512: at line 1
at
oracle.apps.fnd.framework.OAException.wrapperInvocationTargetException(OAExce
ption.java:996)
at
oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:211)
at
oracle.apps.fnd.framework.server.OAUtility.invokeMethod(OAUtility.java:153)
at
oracle.apps.fnd.framework.server.OAApplicationModuleImpl.invokeMethod(OAAppli
cationModuleImpl.java:761)

## Detail 0 ##
java.sql.SQLException: ORA-20001:
ORA-06512: at «APPS.HR_ASSIGNMENT_API», line 607
ORA-06512: at line 1

STEPS
————————
The issue can be reproduced at will with the following steps:
1. Login to the application and select US HRMS Manager responsibility.
2. Query for an employee and terminate on a future date (for example, terminate1 year after the system date).
3. Launch the employee site visitor page and login as the above employee as mentioned in step 2.
4. Search for a job and apply for that job.
5. Login as the recruiter of the above vacancy in which the employee applicant has applied.
6. Navigate to the vacancy tab and search for the above vacancy.
7. Navigate to the View Applicants for the vacancy page.
8. Click on the employee applicant name and navigate to the Candidate Profile — Applications tab.
9. Change the status of the Application to «Terminate Application.»
10. Save the record.
11. After the employee applicant is successfully terminated, recruiter tries to reconsider the application. Navigate to the vacancy View Applicants page, check the Rejected Applicants checkbox and click on GO button. This will return the above employee applicant who has been terminated.
12. Select the applicant record and click on Reconsider Application button.
Go through the steps and while submitting the transaction, the application shows an error message.

Cause

To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Oracle offers a comprehensive and fully integrated stack of cloud applications and platform services. For more information about Oracle (NYSE:ORCL), visit oracle.com. пїЅ Oracle | Contact and Chat | Support | Communities | Connect with us | | | | Legal Notices | Terms of Use

Источник

ORA-20001 Seen When Running Datapatch due to Incorrect Dpload.sql Script (Doc ID 2468073.1)

Last updated on SEPTEMBER 04, 2022

Applies to:

Symptoms

When applying or rolling back a patch that contains a faulty version of dpload.sql, various unexpected results or errors may occur, especially in a CDB environment.
The ORA-20001 error is one possibility but there might be other manifestations, not all of which can be predicted.

There are cases when a Database Bundle Patch or PSU has a correct dpload.sql in the apply path, but in the rollback files, it has an incorrect dpload.sql script which contains the improper connect statement:
utl_file.put_line(h, ‘connect sys/