Hello,
We had and issue with the NDP.
The error log is :
0927 06:00:19.42 CD: checkerr(StructLogin=22336f70) - Error, ORA-00955: name is already used by an existing object
ORA-06512: at "CTMUSER.CLEAN_AJF", line 496
ORA-06512: at line 2
0927 06:00:19.42 CD: ExecDML() - Failed in OCIStmtExecute
0927 06:00:19.42 CD: BEGIN
clean_ajf('20090927','060017','CD','NOT_KEEP');
END;
Please help on this issue. On this day no jobs were removed from the AJF.
i Would like to know what is process ie script used for NDP.
Please help on this.
Regards,
Satish
Control-m NDP issue
-
baralem
Hi, i've found a kb in BMC support page that aparently resolves this issue. Hope this helps.
regards.
martin
http://rkm.bmc.com/rkm/viewdoc.jsp?reme ... elf%20Help
Details
Self Help Document
ID: KM-000010041461
Type: Problem Solution
Problem
CONTROL-M/Server New Day has completed but we still see all yesterdays jobs in addition to todays jobs.
The following error msg is seen Oracle alert file:
Bug 3043312 ORA-38301: CAN NOT PERFORM DDL/DML OVER OBJECTS IN RECYCLE BIN
In ~/ctm/proclog you will find the following error msg in the CD log:
0712 07:00:23.23 CD: checkerr(StructLogin=21324f88) - Error, ORA-00955: name is already used by an existing object
ORA-06512: at "CTMUSER.CLEAN_AJF", line 493
ORA-06512: at line 2
0712 07:00:23.30 CD: ExecDML() - Failed in OCIStmtExecute
0712 07:00:23.31 CD: BEGIN
clean_ajf('20070712','070019','CD','KEEP'); NOTE - make a note of this record, you may need it to resolve this issue
END;
Product
CONTROL-M/Server for Unix and Microsoft Windows version 6.3.01
CONTROL-M/Server for Unix and Microsoft Windows version 6.2.01
Environment
Oracle 10
Solution
Apply the latest fix packs for your version of CONTROL-M/Server. This issue is resolved in 6.3.01 Fix Pack 3 and 6.2.01 Fix Pack 4. Even if you apply the fix packs identified, you will likely still need to complete the following steps to clean up any issues from prior day(s).
If your CONTROL-M/Server uses Oracle as it's database this problem can be caused by Oracle 10.1 and 10.2 bug 3043312:- Bug 3043312 ORA-38301: CAN NOT PERFORM DDL/DML OVER OBJECTS IN RECYCLE BIN. The corresponding BMC bug ID is CAR00035228 has been resolved. (see above).
After applying the appropriate fix pack, take the following steps to clean up this issue
Note - if you are not using a BMC bundled Oracle instance consult your Oracle DBA before applying this resolution.
(1) If you have any concerns regarding jobs remaining in error from yesterday running then from the O/S command prompt
when logged on as the CONTROL-M/Server owner run command -
ctmsuspend -s
to prevent CONTROL-M/Server submitting any further jobs.
(2) Note - if you are at liberty to stop and restart Oracle at this time you can go to (3)
Logon to Oracle as the system account (or equivalent) -
sqlplus system/<password>
and execute command on 10.1 Oracle Server
for Oracle 10.2 please replace every occurrence of _recyclebin with recyclebin (no underscore) and run the command from an Oracle 10 client since some of the below syntax will not work on an Oracle 9 client.
SQL> alter system set "_recyclebin" = FALSE;
This is a dynamic setting which disables the recyclebin feature without the need to restart Oracle.
Now empty the recycle bin objects by running command:-
SQL> PURGE DBA_RECYCLEBIN;
now exit sqlplus.
(3) In order to permanently disable the recyclebin locate your for init<ORACLE_SID>.ora file (typically found at oracle/admin/<ORACLE_SID>/pfile/init<ORACLE_SID>.ora)
and replace the record on Oracle 10.1 (for Oracle 10.2 drop the underscore in front of _recyclebin) -
_recyclebin=true
with
_recyclebin=false
If you did not carry out (2) you must now stop CONTROL-M/Server and any other products or applications using the Oracle server and restart Oracle before restarting the other products/applications to make the recyclebin=false setting active.
(4) Unless you have been able to delete all the jobs left in error by using the EM GUI interface or the CONTROL-M/Server utility ctmpsm you will now need to delete as a minimum all Cyclic jobs and jobs that have not executed with yesterdays ODATE.
(5) When a New Day procedure fails it may leaves behind some temporary tables. These tables need to be dropped by logging on to the Database server as CONTROL-M/Server user (DBO).
a. In CONTROL-M/Server account the command
SQL
b. type the following commands when you get the SQL prompt
drop table CMR_AJF_SAVE;
drop table SAVE_DATA_TAB;
c. exit
(6) If you carried out (1) you now need to run from the O/S command prompt when logged on as the CONTROL-M/Server:-
ctmsuspend -r
regards.
martin
http://rkm.bmc.com/rkm/viewdoc.jsp?reme ... elf%20Help
Details
Self Help Document
ID: KM-000010041461
Type: Problem Solution
Problem
CONTROL-M/Server New Day has completed but we still see all yesterdays jobs in addition to todays jobs.
The following error msg is seen Oracle alert file:
Bug 3043312 ORA-38301: CAN NOT PERFORM DDL/DML OVER OBJECTS IN RECYCLE BIN
In ~/ctm/proclog you will find the following error msg in the CD log:
0712 07:00:23.23 CD: checkerr(StructLogin=21324f88) - Error, ORA-00955: name is already used by an existing object
ORA-06512: at "CTMUSER.CLEAN_AJF", line 493
ORA-06512: at line 2
0712 07:00:23.30 CD: ExecDML() - Failed in OCIStmtExecute
0712 07:00:23.31 CD: BEGIN
clean_ajf('20070712','070019','CD','KEEP'); NOTE - make a note of this record, you may need it to resolve this issue
END;
Product
CONTROL-M/Server for Unix and Microsoft Windows version 6.3.01
CONTROL-M/Server for Unix and Microsoft Windows version 6.2.01
Environment
Oracle 10
Solution
Apply the latest fix packs for your version of CONTROL-M/Server. This issue is resolved in 6.3.01 Fix Pack 3 and 6.2.01 Fix Pack 4. Even if you apply the fix packs identified, you will likely still need to complete the following steps to clean up any issues from prior day(s).
If your CONTROL-M/Server uses Oracle as it's database this problem can be caused by Oracle 10.1 and 10.2 bug 3043312:- Bug 3043312 ORA-38301: CAN NOT PERFORM DDL/DML OVER OBJECTS IN RECYCLE BIN. The corresponding BMC bug ID is CAR00035228 has been resolved. (see above).
After applying the appropriate fix pack, take the following steps to clean up this issue
Note - if you are not using a BMC bundled Oracle instance consult your Oracle DBA before applying this resolution.
(1) If you have any concerns regarding jobs remaining in error from yesterday running then from the O/S command prompt
when logged on as the CONTROL-M/Server owner run command -
ctmsuspend -s
to prevent CONTROL-M/Server submitting any further jobs.
(2) Note - if you are at liberty to stop and restart Oracle at this time you can go to (3)
Logon to Oracle as the system account (or equivalent) -
sqlplus system/<password>
and execute command on 10.1 Oracle Server
for Oracle 10.2 please replace every occurrence of _recyclebin with recyclebin (no underscore) and run the command from an Oracle 10 client since some of the below syntax will not work on an Oracle 9 client.
SQL> alter system set "_recyclebin" = FALSE;
This is a dynamic setting which disables the recyclebin feature without the need to restart Oracle.
Now empty the recycle bin objects by running command:-
SQL> PURGE DBA_RECYCLEBIN;
now exit sqlplus.
(3) In order to permanently disable the recyclebin locate your for init<ORACLE_SID>.ora file (typically found at oracle/admin/<ORACLE_SID>/pfile/init<ORACLE_SID>.ora)
and replace the record on Oracle 10.1 (for Oracle 10.2 drop the underscore in front of _recyclebin) -
_recyclebin=true
with
_recyclebin=false
If you did not carry out (2) you must now stop CONTROL-M/Server and any other products or applications using the Oracle server and restart Oracle before restarting the other products/applications to make the recyclebin=false setting active.
(4) Unless you have been able to delete all the jobs left in error by using the EM GUI interface or the CONTROL-M/Server utility ctmpsm you will now need to delete as a minimum all Cyclic jobs and jobs that have not executed with yesterdays ODATE.
(5) When a New Day procedure fails it may leaves behind some temporary tables. These tables need to be dropped by logging on to the Database server as CONTROL-M/Server user (DBO).
a. In CONTROL-M/Server account the command
SQL
b. type the following commands when you get the SQL prompt
drop table CMR_AJF_SAVE;
drop table SAVE_DATA_TAB;
c. exit
(6) If you carried out (1) you now need to run from the O/S command prompt when logged on as the CONTROL-M/Server:-
ctmsuspend -r