Archive for December, 2019
You Need To Forgive Yourself For You Sins
December 31st, 2019, posted in DC Comic And MoviesNID-00135: There are number active threads.
December 29th, 2019, posted in Oracle QueriesNID-00135: There are number active threads.
SQL> select name,open_mode from v$database; NAME OPEN_MODE --------- -------------------- PROD MOUNTED [oracle@oracle sujeet$ nid TARGET=SYS/sys123 DBNAME=PROD SETNAME=YES DBNEWID: Release 11.1.0.7.0 - Production on Thu Apr 26 18:04:18 2018 Copyright (c) 1982, 2007, Oracle. All rights reserved. Connected to database ACSEBSP (DBID=2199446376) Connected to server version 11.1.0 NID-00135: There are 1 active threads Change of database name failed during validation - database is intact. DBNEWID - Completed with validation errors.
Solution :
Action: Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again.
SQL> alter database open; Database altered. SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down. SQL> startup mount ORACLE instance started. [oracle@oracle sujeet$ nid TARGET=SYS/sys123 DBNAME=PROD SETNAME=YES
apps-fnd-01564 oracle error 1653 in summit others
December 22nd, 2019, posted in Oracle QueriesCAUSE :
Typically occurs when writing a new record to oracle database, but there is not enough space to write it. The data file in oracle tablespace called APPS_TS_TX_DATA should be set to AUTOEXTEND. If it is not, Oracle will not auto-increase the size of the datafile, and will raise the above error.
SOLUTION :
If all the reports end in COMPLETE – NORMAL, means its work.
If not than follow below steps.
Run a Concurrent Manager Recovery :
1. Please stop Concurrent managers by adcmctl.sh.
2. If not stopped, please abort managers by adcmctl.sh.
adcmctl.sh abort apps/****
3. Please kill if a process remains.
4. relink all (ADADMIN)
5. Please retry Concurrent Manager Recovery.
Navigate :
Oracle Applications Manager > Concurrent Managers OR Concurrent Requests > Site Map > Diagnostics and Repair > Concurrent Manager Recovery.
OR
SOLUTION :
WARNING: This procedure should be performed by your ORACLE Database Administrator.
The SYSTEM user should have required privileges to perform this task.
Enable Autoextend on the APPS_TS_TX_DATA tablespace by executing the following Oracle PL/SQL command:
SQL > ALTER DATABASE DATAFILE '/u01/ORACLE/ORADATA/APPS_TS_TX_DATA.ORA' AUTOEXTEND ON NEXT 3072K
ORA-39142: incompatible version number 5.1 in dump file
December 16th, 2019, posted in Oracle QueriesPROBLEM :
Trying to export schema/tables from higher Database version 12.2.0.1.0 and import to version 12.1.0.1.0, causing following error message.
ERROR :
Import: Release 12.1.0.2.0 - Production on Thu Jun 13 17:03:18 2019 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options ORA-39001: invalid argument value ORA-39000: bad dump file specification ORA-39142: incompatible version number 5.1 in dump file "/u01/expimp/schemas_name.dmp"
SOLUTION :
Please set parameter Version=12.1 in export command and import the data without issue.
Source Database (12.2.0.1) :
expdp system/****@prod schemas=schemas_name Version=12.1 directory=EXPDP dumpfile=schemas_name.dmp log=schemas_name.log expdp system/****@PROD directory=EXPDP tables=table_name Version=12.1dumpfile=schemas_name.dmp log=schemas_name.log
Target Database (12.1.0.1) :
impdp system/****@prod directory=EXPDP schemas=schemas_name dumpfile=schemas_name.dmp logfile=schemas_name.log impdp system/****@PROD directory=EXPDP tables=table_name dumpfile=schemas_name.dmp log=schemas_name.log
