Error in job REFRESH_ADMIN_DATA_FROM_SUPPORT

Hi,
We are facing errors in REFRESH_ADMIN_DATA_FROM_SUPPORT. It fiished successfully but contain errors as below.
Job started
Step 001 started (program AI_SC_REFRESH_READ_ONLY_DATA, variant , user ID WF-BATCH)
No system headers will be generated in SMSY from SAP Support Portal
The following error messages have been returned by SAP Support Portal:
No system BWS found for installation number XXXXX
No system CNB found for installation number XXXX
No system DEP found for installation number XXXX
No system QEP found for installation number XXXXX
No system SBX found for installation number XXXX
Installation number 000INITIAL not found
No system UEP found for installation number XXXX
Job finished
Please let me know if I have to change anything.
Best Regards,
Tushar

Hi,
you can doubleclick the messages in the Job Log to see details.
"No system headers will be generated in SMSY from SAP Support Portal" is fine. Generating Systems in SMSY from SAP Support Portal is only an option for Service Providers that have no other option to get the systems of their customers.
"No system BWS found for installation number XXXXX" indicates that either installation number has not been maintained correctly in SMSY or that the system has been moved to another installation or that the system itself has been deleted in SAP Support Portal. You can fix all this in SMSY.
"Installation number 000INITIAL not found" means that 000INITIAL is not a valid installation number.You can fix this in SMSY.
Regards
Andreas

Similar Messages

Error Job REFRESH_ADMIN_DATA_FROM_SUPPORT - Business Partner error

Hello gurus,
System: Solution Manager 7.0 Ehp1 SPS22 (win 2008 + SQL Server 2005)
The problem is... I've been setting up the service desk for VAR option. We, our company, are VAR and the main goal for this configuration is link our own solution manager with our customers in order that they can send some messages to us asking for help. This type of service as you, is the Service Desk for VAR which runs on solution manager system.
So in this point, we are in phase of configuration of customer numbers and system numbers of all systems that customers have in your landscape.
We´re faccing with a problem about JOB - REFRESH_ADMIN_DATA_FROM_SUPPORT - the job that collects information from SAP Marketplace of customers. And this job log have some error, namely we couldn´t create a Business Partner which are necessary further for maintenance business partner (tcode BP) and for IBASE generate!
As you see in following image we have that error after that job runs:
http://img263.imageshack.us/img263/3233/businesspartner.jpg
09.04.2010 22:01:01 Business partner for customer number 813324 could not be created AI_SC_EN 137
For your information, the customer number for our customer is 813324 and our customer number is 891916!
I already check some view/tables, such the tables V_AIINSNRS ; V_AISAPCUSTNOS and also the tcode AISUSER, and they seems to me well.
Can you help me how can I solve that error.. on job!???
Best regards,
João Dimas - Portugal

Hello Fabricius Zatti,
Thank you for your answer, but that isn´t the solution for this problem. I already update that note 1023598...
The other note 1350853 is not for my release, the correction of this note is delivered in Support Package SAPKITL431... my system has the last Suport Package Stack which is 22!! (SAPKITL432) So the correction of that note is already suported in system!
Next I´ll show you what I have in tables v_aisapcustnos ; v_aiinsnrs:
http://img97.imageshack.us/img97/8554/vaisapcustnos.jpg
http://img97.imageshack.us/img97/272/vaiinsnrs.jpg
And the transaction aisuser:
http://img97.imageshack.us/img97/8662/aisuser.jpg
In that tables and transaction are some data that is related and relevant for that JOB - REFRESH_ADMIN_DATA_FROM_SUPPORT
Someone help me please.
Best regards,
João Dimas - Portugal

Driver program for adobe form error no job started

Hi
Iwhen I execute driver program for adobe form the program generates error no job started.
the print dialog box appears but when I pressed print preview button it generates this error no job started.
I don't know why it's happening please help.

Hi
Iwhen I execute driver program for adobe form the program generates error no job started.
the print dialog box appears but when I pressed print preview button it generates this error no job started.
I don't know why it's happening please help.

Error reading job logs of Apps server from Central Instance

Dear Gurus,
We have newly installed system with one CI ( cluster environment) and 2 application Instances.
Systems are recently installed by other team. I am looking into support part after handover.
We have noticed below error while reading failed background job logs from our CI. If suppose any job is failing, we can read respective job log from that application instance but it throws error while reading job log from CI to either of application instance.
I checked /sapmnt/SID/global is shared among all 3 servers and i am successfully able to "Touch a" from applications instances.
Even though i have given "777" permissions to all folders like /sapmnt/SID , /sapmnt/SID/global , /sapmnt/SID/global/400JOB*
I am not able to read job log from CI , for same failed job I can read job log from respective application instance.
Error log :
Error reading job log JOBLGX00080700X39290
Message no. BT167
Diagnosis
The background processing system was unable to read the job log named in the message.
This message suggests that there is a problem with the TEMSE storage system of the SAP system. The TEMSE storage system is a repository for temporary objects, such as job logs and spool requests. Job logs are always stored in the TEMSE as operating system files.
This error occurs if the TEMSE system is not able to find or access the file that contains the text of the job log that you requested. Possible causes for the loss or unavailability of the job log include the following:
Someone deleted the required TEMSE file (from the operating system, not from within the SAP system).
A CRON (or equivalent scheduler) job has deleted the TEMSE file.
The file system in which the TEMSE stores its files is not mounted or is not accessible (NFS problem, disk failure, or similar problem).
The TEMSE reorganize or consistency check functions were used within the SAP system and deleted the job log.
SM21 logs :
Error 2 for write/read access to a file. File = /usr/sap/SID/SYS/global
BP_JOBLOG_SHOW: Failed to display jobs. Reason:
> Error reading job log JOBLGX00080700X39290
Strange this is I can check failed job log on one application instance frfom other application instance but not from CI.
Kindly throw some lights where to check.
Regards,

Hi Shravan,
I guess it is related to permission to /sapmnt/SID/global folder. Please ensure owner is sidadm:sapsys in all the systems viz CI, App servers etc.
Check the mounting options are correctly set with read/write mode.
Hope this helps.
Regards,
Deepak Kori

Error saving job to database for standard jobs scheduling

Hi,
In IDES server when iam goto Tr.code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
Error saving job to database
Message no. BT117
Diagnosis
The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
System Response
Job not saved and not scheduled.
Procedure
To analyze this problem, start by checking the system log for messages about network or database problems. You can also use the computing center management system to check your system for problems.
Guide me for the same.
Thanku

HI,
Sometimes this error will come.
Try to schedule jobs manually using SM36 instead of using standard job button.
Also you can check this thread
Re: Error saving job SAP_REORG_JOBS to database
Which seems to report same problem.
Its nothing to take with database conenctivity as SAP is up and running .
Try this and revert.
Regards,

Error Generating Job in LBWE

Hi BWers,
In R/3 Production Server, I start LBWE, and click on the Job Control.
Then I customized the period values, click check and click SAVE.
Then I click the button schedule job, but there is an error message which
says error generating job.
Could you pls help me out, its urgent
Thanks,
Bhima

Hi,
Check the log in SM37 if you are running the job in background.
Make sure there are no entries in the extraction queue and also delta queue is empty. Make sure you do this for all the clients in the source system.
Also make sure that the extractor is active.
Cheers,
Kedar

Error Generating Job

Hi ,
In LBWE when I try to do the job control, its giving me an error saying "Error generating Job". This is a new installation of BW 3.5. How do I fix this error.
Thank You,
Rao

Hi Michael,
I dont get this error as a dump, but its comes up with a red cross mark on the bottom toolbar. I did not find anything in ST22 and SM21.
Thank You,
Harini.

Got error in job execution, but the standalone procedure runs fine.

I got error in job execution. But it runs fine as standalone procedure. Where could it be wrong?
_>exec dbms_job.run(145373);
BEGIN dbms_job.run(145373); END;
ERROR at line 1:
ORA-12011: execution of 1 jobs failed
ORA-06512: at "SYS.DBMS_IJOB", line 481
ORA-06512: at "SYS.DBMS_JOB", line 275
ORA-06512: at line 1
I checked the alert log file
ORA-06550: line 1, column 101:
PLS-00103: Encountered the symbol "RPTIMPORT" when expecting one of the following:
:= . ( @ % ;
Thu May 2 12:59:34 2013
Errors in file /oracle/admin/PDAMLPR1/udump/pdamlpr11_ora_15574.trc:
ORA-12012: error on auto execute of job 146925
ORA-06550: line 1, column 133:
PLS-00103: Encountered the symbol "" when expecting one of the following:
:= . ( @ % ;
The symbol ";" was substituted for "" to continue.
The trace file:
*** ACTION NAME:() 2013-05-02 12:43:48.261
*** MODULE NAME:(SQL*Plus) 2013-05-02 12:43:48.261
*** SERVICE NAME:(SYS$USERS) 2013-05-02 12:43:48.261
*** SESSION ID:(1811.10644) 2013-05-02 12:43:48.261
*** 2013-05-02 12:43:48.261
ORA-12012: error on auto execute of job 145373
ORA-06550: line 1, column 133:
PLS-00103: Encountered the symbol "" when expecting one of the following:
:= . ( @ % ;
The symbol ";" was substituted for "" to continue.
*** ACTION NAME:(********* Schedule Job: Report C) 2013-05-02 12:47:58.178
*** MODULE NAME:(PATIENT_REMEDIATE_JOB) 2013-05-02 12:47:58.178
*** 2013-05-02 12:47:58.178
ORA-12012: error on auto execute of job 145373
ORA-06550: line 1, column 133:
PLS-00103: Encountered the symbol "" when expecting one of the following:
:= . ( @ % ;
The symbol ";" was substituted for "" to continue.
*** 2013-05-02 12:52:43.409
ORA-12012: error on auto execute of job 146924
ORA-06550: line 1, column 101:
PLS-00103: Encountered the symbol "RPTIMPORT" when expecting one of the following:
:= . ( @ % ;
*** 2013-05-02 12:59:34.651
ORA-12012: error on auto execute of job 146925
ORA-06550: line 1, column 133:
PLS-00103: Encountered the symbol "" when expecting one of the following:
:= . ( @ % ;
The symbol ";" was substituted for "" to continue.
~
~
The job was created as the following with 30 min interval:
The job number: 145373
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job => X
,what => 'RPTIMPORT.pr_exec_pop_ddl21_data_irt'
,next_date => to_date(sysdate)
,interval => '/*30:Mins*/ sysdate + 30/(60*24)'
,no_parse => TRUE
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
END;
Thanks for help!

the issue is resolved. I missed to put ";" at end of what statement. Thank all.

ERROR: replicator: Job Failed :error retrieving site manifest exception

Hi all,
I have installed the Site Studio Publishing utility on content Server machine.
I have installed the site studio publishing client on my machine and I have configured successfully. I mean to say that I have configured the destination on Publishing Utility & Content Provider on Publishing Client.
I have created the publishing job on the the site. I could see the content delivered on my machine from the content server, successfully. Now i have updated the site in the Site designer. I have just added "Hi" in the site layout page in the site designer. I have saved it. Now I have given the publishing job again. While running the job, I am getting following Error:
WARNING: replicator: 401 response received from server
[Sep 13 18:11:49] ERROR: replicator: Job Failed :error retrieving site manifest exception:
com.kinecta.net.HttpIOException: HTTP 401 error received from server :http://10.16.21.124/idc/idcplg?IdcService=SS_GET_SITE_PUBLISH_REPORT&siteId=TestSite
     at com.kinecta.replicator.SiteCrawler.openConnection(SiteCrawler.java:515)
     at com.kinecta.replicator.SiteCrawler.openConnection(SiteCrawler.java:191)
     at SiCloneSyndicator.SiCloneSiteStudioPackageGenerator.getSiteManifest(SiCloneSiteStudioPackageGenerator.java:452)
     at SiCloneSyndicator.SiCloneSiteStudioPackageGenerator.onReplicationStart(SiCloneSiteStudioPackageGenerator.java:342)
     at SiClone.SiCloneSiteReplicator.run(SiCloneSiteReplicator.java:534)
     at SiClone.SiCloneIcePackageGenerator.run(SiCloneIcePackageGenerator.java:39)
     at SiClone.SiCloneSiteReplicatorRunner.runJob(SiCloneSiteReplicatorRunner.java:308)
     at SiClone.SiCloneSiteReplicatorRunner.run(SiCloneSiteReplicatorRunner.java:178)
     at SiCloneSyndicator.SiCloneGenerator.doUpdate(SiCloneGenerator.java:516)
     at SiCloneSyndicator.SiCloneGenerator$1.run(SiCloneGenerator.java:472)
First of all, May i ask you a question: What is the site manifest file?
Any help would be much appriciated.
Regards & thanks,
Nirmala Vijaya Sekhar varre

Hi Sreenath,
I am getting following error while publishing the microsite using Site Studio Publisher even I unchecked "Treat home page errors as critical" and "Treat manifest errors as critical" options, here is the log:
INFO 2012-02-14 07:35:11,794 - ----- Running Job
INFO 2012-02-14 07:35:11,794 - Output Path : /opt/ora/ucmdev/Middleware/domains/UCMDevDomain/ucm/cs/data/SiteStudioPublisher/output/MyBiopsy
INFO 2012-02-14 07:35:11,794 - Authentication : BasicAuth
INFO 2012-02-14 07:35:11,794 - Use Cache Control : false
INFO 2012-02-14 07:35:11,794 - Publish Now : false
INFO 2012-02-14 07:35:11,794 - Force Analyze : false
INFO 2012-02-14 07:35:11,794 - Force Download : false
INFO 2012-02-14 07:35:11,794 - Use LastModified : true
INFO 2012-02-14 07:35:11,794 - Use SSPETag : true
INFO 2012-02-14 07:35:11,794 - Treat home page errors as critical : true
INFO 2012-02-14 07:35:11,794 - Treat manifest errors as critical : true
INFO 2012-02-14 07:35:11,794 - Soft Error Threshold : 99
INFO 2012-02-14 07:35:11,794 - Soft Error Codes : 403,404
INFO 2012-02-14 07:35:11,794 - Hard Error Threshold : 99
INFO 2012-02-14 07:35:11,794 - Hard Error Codes : 501,502
INFO 2012-02-14 07:35:11,794 - Delete Threshold : -1
INFO 2012-02-14 07:35:11,794 - Friendly Url Parameters :
INFO 2012-02-14 07:35:11,794 - Dynamic Url Parameters :
INFO 2012-02-14 07:35:11,794 - Default Filename : index.html
INFO 2012-02-14 07:35:11,794 - Page Extension : html
INFO 2012-02-14 07:35:11,795 - ----- Connecting: http://dappucm07.cap.org:16200/cs/idcplg?IdcService=SS_GET_PAGE&siteId=MyBiopsy
INFO 2012-02-14 07:35:11,802 - Response: 301 Moved Permanently
INFO 2012-02-14 07:35:11,802 - http redirect found:http://dappucm07.cap.org:16200/MyBiopsy/index.html
FATAL 2012-02-14 07:35:11,840 - sitestudiopublisher.net.IOFailureException: error retrieving site manifest
INFO 2012-02-14 07:35:11,840 - Error threshold exceeded
INFO 2012-02-14 07:35:11,840 - Finishing...
INFO 2012-02-14 07:35:11,840 - ----- Job Summary
INFO 2012-02-14 07:35:11,840 - Source URL : http://dappucm07.cap.org:16200
INFO 2012-02-14 07:35:11,840 - Start time : Tue Feb 14 07:35:11 CST 2012
INFO 2012-02-14 07:35:11,840 - End time : Tue Feb 14 07:35:11 CST 2012
INFO 2012-02-14 07:35:11,840 - Duration : 0 hours 0 minutes 0 seconds 46 milliseconds
INFO 2012-02-14 07:35:11,840 - Connect Time : 0:00:00.046
INFO 2012-02-14 07:35:11,840 - ----- Links Summary
INFO 2012-02-14 07:35:11,840 - Total : 0
INFO 2012-02-14 07:35:11,840 - Modified : 0
INFO 2012-02-14 07:35:11,840 - Added : 0
INFO 2012-02-14 07:35:11,840 - Deleted : 0
INFO 2012-02-14 07:35:11,840 - Examined : 0
INFO 2012-02-14 07:35:11,840 - Redirected : 0
INFO 2012-02-14 07:35:11,840 - Downloaded : 0
INFO 2012-02-14 07:35:11,840 - Not Found : 0
INFO 2012-02-14 07:35:11,840 - ----- Job Failed
INFO 2012-02-14 07:35:11,840 -

Logging errors from job's program

Hello,
I want to log error returned from the job's program and I wonder whether it is possible at all.
What I have done is:
1) write a procedure
2) create a program executing this procedure
3) create a job running this program
From time to time this procedure returns error (it does some operation on objects and sometimes some of them are invalid). Normally, this error causes job to finish it's action (job failure as well). I needed this job to proceed so I added a clause 'exception when others then null'. Now it works, but it's a temporary solution because I need to capture this error and log it, so that it is available for further investigation.
I searched through oracle doc and it seems the only choice is to create my own table or file and log the results into it.
Does any of you know any other way? For example to log it in somehow into system tables (like dba_scheduler_job_run_details).
Thanks in advance,
Aliq

Hi Dharmesh,
Thanks for responding.
This is a large deployment involving hundreds of applications and servers. My responsibility is to come up with development guidelines for applications hosted on TS. I have gone through the guidelines
posted by Microsoft @
http://msdn.microsoft.com/en-us/library/aa383490(v=vs.85).aspx. But it didn't cover the topic on logging.
Do you know whether Microsoft has published any other document on this topic.
Thanks,
Raj

Error saving job to database

Hi,
In IDES ECC6.0 Ehp 3 (Os: window 2003 64bit DB: oracle 10.2.0.2) server when iam goto T-Code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
<error saving job to database>
So I patched oracle 10.2.0.1 to 10.2.0.4, and kernel patch with latest one.
But, the same error occured.
I tried to execute r3trans -d at the OS level,the results is <The system cannot execute the specified program>.
In SM21, i am getting below error
<error saving job to database>
&CAUSE &
The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
&SYSTEM_RESPONSE&
Job not saved and not scheduled.
&What_TO_DO&
To analyze this problem, start by checking the <DS:TRAN.SM21>system log for message about network or database problems. you can also use the <DS:TRAN.SRZL>computing center management system to check your system for problems. >
I checked SM28 and SICK and it reports no error.
Please help how can I schedule the standard jobs

Make sure you use the proper kernel, for 64bit there are two kernels:
- one for AMD64 and Intel64
- one for Itanium-2 64bit
The R3trans seems to be the wrong one - as I would suggest are the brtools.
Markus

Redwood User Account error on Job

Hi All,
We currently had all our BWP jobs fail with the following error:
JCS-00503: OS account SYSJCS does not exist or is disabled on BRSAPPRDBWPV2
JCS-00315: job must run under OS equivalent of Oracle account SYSJCS
We run our oracle database on a Windows 2003 environment and also our Redwood/SAP servers are on a Windows 2003 server.
The job itself users "USER" account.
The only way we could get the jobs to start was by restarting the BWP Redwood services, and this worked fine.
Also want to state the we had the following issue at the sametime which was flagged up to us in "messages":
resubmit.update_job:
ORA-04061: existing state of package body "SYSJCS.CHAIN" has been invalidated
ORA-04065: not executed, altered or dropped package body "SYSJCS.CHAIN"
ORA-06508: PL/SQL: could not find program unit being called: "SYSJCS.CHAIN"
All our BWP process chains are executed via the RUN BW CHAIN script, which is copied and renamed for the process chain.
We have tried to replicate the error in our dev environment but it worked fine. RFC points nothing at all.. Any help would be much appreciated. OSS note has been raised...
Thank You
Jazz

Hi Jazz,
The SYSJCS.CHAIN package is not used for BI Process Chains, only for CPS Chains. So the invalidation must have come from another source.
When this error occurs, as long as there are sessions started before the package has been re-validated (state reinitialized), you can continue to run into this error until all sessions have been restarted. The extend of the error depends on the package being reinitialized (how often it is used and the dependencies it has) and the session that needs to call it.
I think the error may already have been there before you did the chain import and just happened to surface shortly after the import.
Regarding your other questions:
1. RSI_IMPORT_BW_CHAINS or RSI_IMPORT_BW_CHAIN_DEFINITIONS:
the second one is only needed if you want to display the process chain definitions in the web interface before the chain is even running in CPS (in the job monitor you only see the processes that have started); if you do not use that, RSI_IMPORT_BW_CHAINS is enough
2. How would you go about maintaining BW process chains in Redwood (CPS)?
This is a question that every customer runs into at some point. First, you currently can not change a process chain definition in the BI system from CPS. Then there are cases where you probably want to leave the process chain structure intact (typically on the deepest level: drop index, do some work, recreate indexes). And there are other cases where it can be useful to bring some logic to CPS (typically on all levels where you have process chain within process chain in BI, ie. on all but the deepest levels).
For this last case, which is of course the most interesting for CPS, it can be very valuable to recreate the BI "meta-chain" structure in a CPS job chain.
So here you replace the BI "meta-chain" calling several BI process chains by a Cronacle job chain still calling some of the BI process chains (the ones on the deepest levels).
Now you can add all the CPS extras for error handling, retries, cross system dependencies, (external) events, alerting, etc. etc. on each and every point in the CPS job chain, so you get a lot more information, intervention and recovery points on your BI process than you would when running the entire thing in one big BI Process Chain (triggered from CPS or not does not matter).
Typically the customer's decision here mainly depends on the advantages that can be achieved, especially if there are service levels to be met on the reports that need to be delivered from BI and these deadlines tend to get tighter by the month.
By reducing the total runtime of the process or reducing the number of errors that occur or if they occur, the amount of work to fix it, you can save a lot of time, and thus money.
Hope this helps.
Regards,
Anton.

Spoll I/O Error on job program

Hi people,
Im havaing a problem in a update program.
Here's what happens.
Im doing a program that update some tables directly trught the update command, one program for each table and I put them into a job(one job for each program, and then run one after te other), because is a lot o lines to update.
Every program runed correctly, but the program that updates de table QMEL gimme a error message.
The message is SPOOL_I/O_ERROR
I saw the log of the job and the error occurs on the WRITE command, I think that is because it will show a lot o lines that it updated and then the spool blasts, but in some tables bigger than QMEL the job runed without problems.
What may be happening and what can i do?
There is some routine to clean the spool before I print the report?
Each job has its spool or they share the same?
    WRITE : 'TABLA : ', p_tabla,
        20 'Seq. : ',p_seq.
    ULINE.
*....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....8....+....9....+....1
*Número de aviso   Material             Gr antes    Gr Despues
*999999999999      999999999999999999   999999999   999999999
    WRITE: /01 'Número de aviso',
             19 'Material',
             40 'Gr antes',
             52 'Gr Despues'.
    ULINE.
    SORT ts_out BY qmnum.
    LOOP AT ts_out.
      WRITE : /01 ts_out-qmnum,
                19 ts_out-matnr,
                40 ts_out-matkl,
                52 ts_out-gran.
Thanks

What hard drive is it? What does the error say, and when do you see it?
- Peter

Error creating job in oracle

I'm having a problem creating a job in oracle . I want at the end of each day to put some values from table1 in table2, empty table1, and then delete and re-create some sequences..because I have auto-increment id and each day I want to sequence to start from 0 again. So long story short I tried creating this job using toad for oracle.
if I just put the first 2 tasks(put data from table1 in table 2, then delete) in the job it works like a charm. if I also add the drop sequence, create sequence I get an error saying
Encountered the symbol "DROP" when expecting one of the following:
begin case declare exit for goto if loop mod null pragma
so this is what I want the job to do:
insert into A(a,b,c) select a2,b2,c2 from B;
delete from A;(so far it would work)
drop sequence ida_seq;
create sequence ida_seq
start with 1
increment by 1
nomaxvalue;
drop sequence idb_seq;
create sequence idb_seq
start with 1
increment by 1
nomaxvalue;
so anybody can give me a clue on why I get the error? maybe if someone can give me a link on how to do oracle jobs..cause if I google "oracle+job" I get only jobs(for work) in oracle...but I don't get stuff related to syntax and how to create jobs in oracle. 10x in advance

If this is a PL/SQL question, then PL/SQL has no 'DROP' or 'CREATE' keywords and you would need to use dynamic SQL with EXECUTE IMMEDIATE.
btw there are various techniques around for resetting a sequence to start again at 1 using ALTER SEQUENCE, rather than dropping and recreating it.

Error creating job into trigger using DBMS_SCHEDULER.

Hi,
I am trying to create job using dbms_scheduler package. I have one trigger on insert event on one table. I am creating job using following syntax.
CREATE OR REPLACE TRIGGER TRG_BI_JOB_CONFIG BEFORE INSERT ON JOB_CONFIG FOR EACH ROW
DECLARE
BEGIN
     DBMS_SCHEDULER.Create_Job(job_name => 'my_job1'
                         ,job_type => 'PLSQL_BLOCK'
                         ,job_action => 'delete_temp'
                         ,start_date => TO_DATE('15-JUL-2003 1:00:00 AM', 'dd-mon-yyyy hh:mi:ss PM')
                              ,repeat_interval => 'FREQ=DAILY'
                         ,enabled => TRUE
                         ,comments => 'DELETE FOR job schedule.');
EXCEPTION
WHEN OTHERS THEN RAISE;
END;
but I am getting following error while inserting into JOB_CONFIG table.
ORA-04092: cannot in a trigger
ORA-06512: at "PRAKASH1.TRG_BI_JOB_CONFIG", line 41
ORA-04088: error during execution of trigger
same above statement If I am running from sqlplus then It is creating job without error. If I am creating job using DBMS_JOB into trigger then It is also working fine but this package is depricated from oracle10g so I cannt use it any more.
My Oracle version is 'Oracle DATABASE 10g RELEASE 10.2.0.1.0 - Production'.
can anyone help me in this context.

I have a few comments on this thread as an Oracle dbms_scheduler developer.
- Oracle takes backward compatibility very seriously. Although dbms_job is deprecated, the interface will continue to work indefinitely. The deprecation of dbms_job is so that customers will be encouraged to take advantage of the more powerful dbms_scheduler. It is extremely unlikely that entire blocks of functionality will ever be removed. There is currently no plan to remove dbms_job functionality (and even if there were, doing so would be strenuously opposed by many users).
- lots of internal Oracle database components are standardizing on using dbms_scheduler (resource manager, materialized views, auto sql tuning etc). This is good evidence that it will continue to be the recommended scheduling method for the foreseeable future - not even the concept of a replacement exists. It is also under active development.
- The reason for the automatic commit is that a dbms_scheduler job is a full database object like a stored procedure or a table. So a call to dbms_scheduler.create_job is like executing a DDL which takes effect immediately. A dbms_job job is mostly just a row in a table so a call to dbms_job.submit behaves like regular DML. There are many advantages to a job being a full database object but DDL behaviour is an unfortunate requirement of this.
Hope this clears a few things up, reply with any questions.
-Ravi

Error in job REFRESH_ADMIN_DATA_FROM_SUPPORT

Similar Messages

Maybe you are looking for