Problem:
After creating an spfile on an 11g instance (11.1.0.7) on R12.1.3 on Windows 2008, it does not automatically appear when the ‘show parameter spfile’ command is issued in SQL*Plus.
Solution:
When the database is started via the Windows Services panel, it seems that the pfile is used by default, even though the spfile may have been created. Stop and start the database via SQL*Plus to see the spfile.
Problem:
Checked alert log file and saw the following errors:
ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_3395507964_562 by 128 in tablespace SYSAUX MMON Flush encountered SYSAUX out of space error(1688). MMON (emergency) purge of WR snapshots (546) and older ORA-1688: unable to extend table SYS.WRH$_ACTIVE_SESSION_HISTORY partition WRH$_ACTIVE_3395507964_562 by 128 in tablespace SYSAUX MMON Flush encountered SYSAUX out of space error(1688). MMON (emergency) purge - nothing to purge, pgsid=0.
Solution:
Add a new datafile to the SYSAUX tablespace.
Problem:
Unable to connect to SQL:
F:oracleVIS12dbtech_st11.1.0>sqlplus / as sysdba SQL*Plus: Release 11.1.0.7.0 - Production on Tue Mar 27 11:31:04 2012 Copyright (c) 1982, 2008, Oracle. All rights reserved. ERROR: ORA-12518: TNS:listener could not hand off client connection
Solution:
Increase PROCESSES initialization parameter.
Use the following command to check the value of the PROCESSES initialization parameter in SQL*Plus:
show parameter processes
If the database was started using an spfile, then the following command can be used to change the PROCESSES initialization parameter to 500:
alter system set processes=500 scope=spfile;
If the database was started using a pfile, then the value of the processes parameter must be changed in the pfile and the database bounced.
[amazon asin=0071780262&template=iframe image&chan=default] [amazon asin=1565922379&template=iframe image&chan=default] [amazon asin=1430236620&template=iframe image&chan=default]
Problem:
After installing 11g on Oracle Linux 5 and running SQL*Plus, the following error appears:
sqlplus: error while loading shared libraries: /u01/app/oracle/product/11.1.0/db_1/lib/libnnz11.so: cannot restore segment prot after reloc: Permission denied
Solution:
Turn off SELinux. As root user, issue the following command:
/usr/sbin/setenforce 0
Problem:
While running patch 9239090, the following error appears:
ATTENTION: All workers either have failed or are waiting: FAILED: file OKLTXRBKUG.sql on worker 1. FAILED: file OKLTXRBKUG.sql on worker 2. FAILED: file OKLTXRBKUG.sql on worker 3. FAILED: file OKLTXRBKUG.sql on worker 4. FAILED: file OKLTXRBKUG.sql on worker 5. FAILED: file OKLTXRBKUG.sql on worker 6. FAILED: file OKLTXRBKUG.sql on worker 7. FAILED: file OKLTXRBKUG.sql on worker 8. FAILED: file OKLTXRBKUG.sql on worker 9. FAILED: file OKLTXRBKUG.sql on worker 10. FAILED: file OKLTXRBKUG.sql on worker 11. FAILED: file OKLTXRBKUG.sql on worker 12. ATTENTION: Please fix the above failed worker(s) so the manager can continue.
Solution:
The OKL_TRANSACTION_PVT package was invalid. When this was compiled, the OKL_SECURITIZATION_PVT was invalid. In this way, a number of OKL packages were invalid and the error was cascading. In order to resolve the issue, I logged on to SQL*Plus and ran the following commands:
alter package APPS.OKL_TXL_ASSETS_PVT compile;
alter package APPS.OKL_TXL_ASSETS_PVT compile body;
alter package APPS.OKL_TXL_ASSETS_PUB compile;
alter package APPS.OKL_TXL_ASSETS_PUB compile body;
alter package APPS.OKL_SPLIT_ASSET_PVT compile;
alter package APPS.OKL_SPLIT_ASSET_PVT compile body;
alter package APPS.OKL_SECURITIZATION_PVT compile;
alter package APPS.OKL_SECURITIZATION_PVT compile body;
alter package APPS.OKL_TRANSACTION_PVT compile;
alter package APPS.OKL_TRANSACTION_PVT compile body;
OKL_TRANSACTION_PVT now compiles without issue.
To resolve this in future, use adadmin to compile APPS schema. Afterwards, issue the following SQL statement in SQL*Plus to get the number of invalid objects:
select count(*) from dba_objects where status = ‘INVALID’;
Continue compiling APPS schema with adadmin and checking the number of invalid objects until that number no longer decreases.
Problem:
EBS instance running out of processes. Need to increase the database PROCESSES initialization parameter.
Solution:
Change the PROCESSES init parameter in the pfile or scope=spfile. Then restart the database (using addbctl.sh, not using the database stop immediate/startup command as shown below).
Problem: When trying to add lines to a Standard RFQ (Request for Quotation), the user encounters the following error:
Could not reserve record [2 tries].
Solution: Kill lock on session.
Problem: The following code runs in SQL Developer and SQL*Plus from the server:
SELECT person_name,
employee_number,
date_from,
date_to,
segment_details
FROM apps.hrfg_detailed_special_info
WHERE to_date('&1', 'RRRR/MM/DD HH24:MI:SS') BETWEEN date_from AND date_to
AND information_type = 'ABC Full Time Payroll Remarks'
AND segment_name = 'Remarks'
ORDER BY person_name
/
However, when it is registered as a concurrent program and run, no output appears.
Solution: The apps_initialize subroutine must be called before running the script.
Problem: After SQL*Plus concurrent job is registered and run, the concurrent job completes in error and the following message appears in the output:
Enter value for 10: EXEC FND_CONC_STAT.COLLECT;
Enter value for 20:
Enter value for 30: EXIT
peed.start_date between to_date('EXEC FND_CONC_STAT.COLLECT;', 'RRRR/MM/DD HH24:MI:SS') and to_date('','RRRR/MM/DD HH24:MI:SS')
*
ERROR at line 18:
ORA-01841: (full) year must be between -4713 and +9999, and not be 0
Solution: The parameters in the SQL script must be changed from ‘&P_Start_Date’, ‘&P_End_Date’ and ‘&P_Payroll’ to ‘&1’, ‘&2’ and ‘&3’.
Problem: While creating a dictionary managed tablespace in Oracle 9i, the following error appears:
SQL> r 1 CREATE TABLESPACE data01 2 DATAFILE '$HOME/oradata/ORCL/data01.dbf' SIZE 2M 3* EXTENT MANAGEMENT DICTIONARY CREATE TABLESPACE data01 * ERROR at line 1: ORA-12913: Cannot create dictionary managed tablespace Solution:
Consulting the Oracle 9i online documentation, the following cause and action is found:
Cause: An attempt was made to create a dictionary managed tablespace in a database whose SYSTEM tablespace is locally managed.
Action: Create a locally managed tablespace.
As a result, the dictionary managed tablespace cannot be created in this Oracle 9i database.
Reference:
http://download.oracle.com/docs/cd/B10500_01/server.920/a96525/e12700.htm
Recent Comments