When a job is scheduled log cannot be seen

Hi All,
Im working in Oracle Warehouse Builder Client & Repository 11.1.0.7.0.
We have some ETL jobs that has to be executed on a daily basis.
But when we schedule the ETL Job, we cannot see the log, i.e. step by step process of the Process Flow.
And the same appears when we manually trigger the job.
Please let me know whether there is a way i can get log file when my job is scheduled.
Thanks in advance
Regards
Prem

Similar Messages

What happens in the background when a job is scheduled!!!

Hi,
Can anyone tell me what exactly happens in the background in SAP when a job is set to "Scheduled" ( sm37) .
Can v see the code executed in the background during the transtion from " Scheduled" state of a job to" Cancelled" to "Complete" state.
Its urgent,
Answers will rewarded,
regards,
Rohan

Hi Rohan,
Jobs and job steps enable you to treat complex tasks as single units. That is, you can schedule several programs needed to complete a particular task as steps within a single job, with the advantage of the job being single logical container for all the steps needed to complete the task. You need to schedule or review only one background job in order to schedule or review any of the individual steps necessary for completing the task.
Assume that a particular data transfer with batch input requires that you start two programs, an external program to prepare the batch-input session and an internal program to process the session. Creating a job made up of two steps lets you handle the two programs as a single unit. Scheduling that one job schedules both programs. The results of each program's run can be seen in the job log.
Some background processing attributes apply to entire jobs and, therefore, to all job steps within a job. For example, the earliest possible start time for any job steps will be the start time for the job. Frequency of repetition, priority, and other global attributes also apply to the whole job.
To ensure that you can flexibly run individual programs, you can set important attributes individually for each job step, too. Each job step can:
have its own spool, or output, specifications
run under the authorizations of a separate user
use a different language
have its own runtime options (for programs external to the SAP System), such as handling of error output and synchronicity
In general, job steps run sequentially and synchronously in the order they're entered in a job: the first step starts, runs, and is completed, then the second step starts, and so on. The only exception is when you schedule an external program to run asynchronously. In this case, the background processing system starts the next job step without waiting for a return code from the external program. If the external program runs long enough, then the start of the next job step may overlap it.
Job steps run partially independently of each others status. That is, the abnormal termination of one job step does not roll back the work of a previously completed job step if this previous step was executing a commit. If any job step fails, however, then the entire job fails. No further job steps are carried out, and the job's status changes to Canceled.
There are two types of job steps:
An executable ABAP program
Only type 1, or executable, ABAP programs can be used as job steps. Module pools and function groups, which are collections of ABAP modules, are not allowed. The specifications required for an ABAP job step are:
ABAP program + Variant + Print and archiving parameters + Language
An external command or external program
This type of job step allows you to run programs outside the SAP System. External commands are predefined, authorization-protected commands for end users. External programs are unrestricted, directly entered commands reserved for system administrators.
The type of external command and external program is unrestricted, meaning that you can use either compiled programs or scripts. Such programs can be run on any computer that can be reached from the SAP System. Parameter passing to non-SAP programs is completely unrestricted except by the predefinition mechanism for external commands.
Output of non-SAP programs, particularly error messages, is included in the job's log file.
Specifications required for an external command or program are:
External command + Type of operating system + (Parameters) + Target host system
External program + Parameters + Target host system
Job Step Language
If your SAP System runs with an Arabic, Cyrillic, or Asian character set, then you may need to change the language specified in the standard background jobs listed above. Languages are assigned to jobs based on job steps. Be sure that the language specified in the job step definition in each of these jobs is set to English (EN).
This change is required because not all languages are available with all code pages. If the jobs specified language is not available, the job will not run.
<b>Reward pts if found usefull :)</b>
Regards
Sathish

SM21:Remote logs cannot been seen.

Dear All,
We have one ECC 6.0 system in our landscape with the below details:
OS :AIX
1. Central Instance (Server1)
2. Application Server 1 (Server2)
3. Application Server2 (server3)
4. Application Server3 (server4)
Below is the problem description:
1. When I execute SM21 and select System Log->Choose->Local System Log, I am able to get the system logs of the logged on server successfully.
2. When I execute SM21 and select System Log->Choose->Remote System Log and try to select another instance name , I cannot find any server.
3. When I execute SM21 and select System Log->Choose->All Remote System Logs. I dont get anything.
As per the SAP Note 25526.I checked the following
1.)On the central server the collector rslgcoll is running as
"co.sapEP1_DVEBMGS00 pf=/usr/sap/EP1/SYS/profile/EP1_DVEBMGS00_onniecpesp03 -F"
2.) In all other Application server the rslgsend is running as
se.sapEP1_D30 pf=/sapmnt/EP1/profile/EP1_D30_onniecaesp02 -F
3.) All the rslg/ parameter has been configured
4.)The global directory has been shared across the System.And the file exits .
Kindly help as to what i have missed.
Regards
Anthony

Hello Anthony,
> 2. When I execute SM21 and select System Log->Choose->Remote System Log and try to select another instance name , I cannot find any server.
>
> 3. When I execute SM21 and select System Log->Choose->All Remote System Logs. I dont get anything.
>
> As per the SAP Note 25526.I checked the following
at very first: central syslog is not remote syslog! So note 25526 will not do anything here
You should execute the function module TH_SERVER_LIST on all application servers (start SM37, insert TH_SERVER_LIST, press F8, press F8 again). As a result you will get a table "LIST", with a mouse click
the contents of the table will be displayed.
In the column "SERV" normally the sapdp* services should be displayed, these are used to connect to the dispatcher of the instance. Most probably you will not see a sapdp<nn> entry but some strange names, e.g. cpq-tasksmart, intraintra, tick-port. In this case please check the /etc/services file of all application servers. All duplicate entries of the interval 3200 to 3299 should be commented out if they are already used for the sapdp<nn> services.
After the restart of the instances the function module should return all sapdp* ports correctly and all remote syslogs should be displayed now.
Regards, Michael

Error when selecting system during scheduling of background job in RAR

Hi,
I am getting an error when I attempt to schedule a background in RAR. It happens when I go to the multiple system selection option. I select a system and click copy. An error example below appears in the logs even when I dont go ahead and schedule the job. The job still runs and returns results when scheduled. However these errors in the logs concern me. Anybody else experience this?
Aug 4, 2010 4:12:32 PM com.virsa.cc.common.util.ExceptionUtil logError
SEVERE: NodeElement(.BatchRiskAnalysisSelection.RoleAnalysisInput.RoleAnalysisSystems): unknown attribute Sign
com.sap.tc.webdynpro.progmodel.context.ContextException: NodeElement(.BatchRiskAnalysisSelection.RoleAnalysisInput.RoleAnalysisSystems): unknown attribute Sign
     at com.sap.tc.webdynpro.progmodel.context.NodeElement.wdGetAttributeInfo(NodeElement.java:374)
     at com.sap.tc.webdynpro.progmodel.context.NodeElement.setAttributeValue(NodeElement.java:877)
     at com.virsa.cc.common.GUIElement.copyAttributes(GUIElement.java:696)
     at com.virsa.cc.common.GUIElement.copyNodeTree(GUIElement.java:792)
     at com.virsa.cc.common.GUIElement.copyNodeTree(GUIElement.java:777)
     at com.virsa.cc.common.ui.MultipleSelectionView.onActionCopy(MultipleSelectionView.java:187)
     at com.virsa.cc.common.ui.wdp.InternalMultipleSelectionView.wdInvokeEventHandler(InternalMultipleSelectionView.java:259)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
Regards,
Niamh

Hi
Did you check the connector whether the background system is connecting or not.
Goto RAR-Configuration>connectors> select the connector of the background system and then press on test connection.
Regards
Hari

Cannot schedule log rotation from LMS32 GUI

All,
I've been experimenting with the log rotation feature from LMS 3.2 UI (CS > Server > Admin > LogRotation) and have noticed when I try to schedule the logrotation with any backup directory (/var/adm/CSCOpx/log for example) it indicates that I cannot schedule it for that directory structure. I even tried /tmp which is wide open for writing from any account but it still errors out.
I am familiar with the logrot.pl -c from the CLI but I need to try this first from the UI. Has anyone run into this before or know if this is a product issue or a mis-configuration on my part?
Regards,
Michael

Exactly what error are you getting when you try and schedule the rotation? You should be able to use both /var/adm/CSCOpx/log and /tmp.

I keep getting an error when trying to update an app- cannot connect to store. I logged out from my account and tried to log back in and got the same error. I am doing all this from my phone since I no longer own a personal computer (only work)

I keep getting an error when trying to update an app- cannot connect to store. I logged out from my account and tried to log back in and got the same error. I am doing all this from my phone since I no longer own a personal computer (only work) since I use iCloud and I tunes match

YAY!!! Saved it in my Mac's Firefox Bookmarks for easy future access!
Hope you are having a lovely afternoon today! I'm about ready to go bobo....I have an early meeting, and I don't want to oversleep! The nice part is that I work remotely, so I only have to wake up 15 minutes or so before the meeting.... I don't even use an alarm clock anymore (really, my iPhone alarm, which is much more pleasant), unless I have to get up at 6:30 or something....
TMI?
GB

I have the new iOS 6 on my iPad, and when ever I try to log on to the iTunes store this comes up: Cannot connect to the iTunes store. Anybody help please? :)

I have the new iOS 6 on my iPad, and when ever I try to log on to the iTunes store this comes up: Cannot connect to the iTunes store. Anybody help please?

I'm also having this problem I've already tried changing the year stuff and its still the same I succeeded once when I toggled my credit card account but after that the same problem occurred.

Scheduler Log - monthly job skipped Apr Monthend

Hello - we have been using the scheduler to run
daily, weekly and monthly reports for a couple of years with no
problems. We are running MX 6.1. Apr 29th I had to stop/restart IIS
and CF. The scheduler log shows the jobs getting 'scheduled'. The
monthly report gets scheduled for May 31, skipping over Apr 30th.
The log says:
"activating2 on Tues Apr 29 09:05 2008 to run on :Sat May 31"
The Monthly scheduled task job say:
"start May 31, 2005 , recurring Monthly at 10:40pm"
any help would greatly be appreciated!! thanks

I apologize if you already solved this.. but see Metalink ID 790221.1
+*<Moderator Edit - deleted contents of MOS Doc - pl do NOT post such content - it is a violation of your Support agreement>*+

BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED

Hello,
To generate the log report, /VIRSA/ZVFATBAK program is scheduled on hourly basis but some time report doesn't get generated and if we see the background job then it shows sucessfully finished.
If we see the maually the log report for FFID then below error message is displayed.
" BACKGROUND JOB WAS NOT SCHEDULED/LOG FILE NOT YET GENERATED"
Can anyone guide me to solve the issue.
Thanks in advance.
Best Regards,
Prashant Dubey

Hi,
once chk the status of the job by selecting that and check job status(cltr+shift_f12)
since it was periodically scheduled job there will be a RELEASED job after every active job..
so try to copy that into another job using copy option and give some new name which u have to remember...
the moment u copy u can find the same copied job in SCHEDULED status...
from here, try to run it again on hourly basis....
After copying the job u can unschedule the old released job to scheduled otherwise 2 will run at a time...
rgds,

Creating a job and scheduling a job error in OEM

Hi, Everyone,
I am trying to create and schedule a job thru OEM. In the the pl/sql block provide i have given my code like this
begin
SET SERVEROUTPUT ON;
SPOOL C:\RFV_PROFILE_REPORT.LOG APPEND;
SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL;
EXEC PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL;
SPOOL OFF;
end;
i have created the job and scheduled it but i am getting this error:
Error # 6550
Details ORA-06550: line 2, column 5: PL/SQL: ORA-00922: missing or invalid option ORA-06550: line 2, column 1: PL/SQL: SQL Statement ignored ORA-06550: line 3, column 7: PLS-00103: Encountered the symbol "C" when expecting one of the following: := . ( @ % ;
could anyone pls help as this is very urgent.
Thanks in advance

Ah, the problem is you are confusing SQLPlus commands with PL/SQL.
SET SERVEROUTPUT ON; -- This is a SQLPlus command, not necessary here.
SPOOL C:\RFV_PROFILE_REPORT.LOG APPEND; -- This is a SQLPlus command, in PL/SQL to write out to a file you will need to call the UTL_FILE package to open a file for writing to. Except that the file you write to will appear on the database server, not your workstation, when the scheduled job runs.
SELECT TO_CHAR(SYSDATE, 'DD/MM/YY HH24:MI:SS') FROM DUAL; -- In PL/SQL you need to SELECT columns INTO variables FROM tables. But in fact I guess you want to write the time to file using UTL_FILE again. However, you don't really need to do this, since scheduler will log the start time and run duration itself.
EXEC PAC_RFV_PROFILE_REPORT.CALL_ALL (200910); -- This is the SQLPlus equivalent of the PL/SQL command:
BEGIN
PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
END;
SPOOL OFF; -- This is a SQLPlus command, not necessary here.
So to summarise, all you really need is:
BEGIN
PAC_RFV_PROFILE_REPORT.CALL_ALL (200910);
END;
And the scheduled job will log the start time and duration in the database, which you can find here:
SELECT * FROM USER_SCHEDULER_JOB_RUN_DETAILS

Dump TSV_LIN_ALLOC_FAILED , when run job : SAP_COLLECTOR_FOR_JOBSTATISTIC

hi all the experts,
When the job SAP_COLLECTOR_FOR_JOBSTATISTIC ,
I searched in service.sap.com notes and have not achieved anything specific.
This is canceled and when I check the st22 said that there is not enough space in memory. annex the dump TSV_LIN_ALLOC_FAILED.
thanks and regards.
Gustavo Gonzalez
ShrtText
No roll memory available to extend the index of an internal table.
What happened?
Each transaction requires some main memory space to process
    application data. If the operating system cannot provide any more
    space, the transaction is terminated.
What can you do?
Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the
    following profile parameters:
o ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement.
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
Error analysis
The linear index of an internal table was supposed to be extended.
However, the 2293776 bytes of memory requested for it were not available
in the roll area.
Storage location: "Session memory"
            Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server sapsrv01_D01_01 on host sapsrv01 (wp 2)"
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1886
How to correct the error
    Decide by analysis whether this request is reasonable or whether there
    is a program error. Pay particular attention to the internal table
    entries listed below.
    The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 1708928
    Extended memory (EM)........... 114982560
    Assigned memory (HEAP)......... 276176080
    Short area..................... " "
    Paging area.................... 24576
    Maximum address space.......... " "
You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "TSV_LIN_ALLOC_FAILED" C
    "RSBPCOLL" or "RSBPCOLL"
    "START-OF-SELECTION"
System environment
     SAP Release.............. "640"
Application server....... "sapsrv01"
     Network address.......... "10.0.0.15"
     Operating system......... "Windows NT"
     Release.................. "5.2"
     Hardware type............ "4x Intel 801586"
     Character length......... 8 Bits
     Pointer length........... 32 Bits
     Work process number...... 2
     Short dump setting....... "full"
Database server.......... "SAPSRV01"
     Database type............ "MSSQL"
     Database name............ "D01"
     Database owner........... "d01"
Character set............ "English_United State"
SAP kernel............... "640"
     Created on............... "Oct 3 2007 00:34:24"
     Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
     Database version......... "SQL_Server_8.00 "
Patch level.............. "203"
     Patch text............... " "
Supported environment....
     Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
     SAP database version..... "640"
     Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
      Windows NT 6.0"
Memory usage.............
Roll..................... 1708928
EM....................... 114982560
Heap..................... 276176080
Page..................... 24576
MM Used.................. 379558912
MM Free.................. 10752584
SAP Release.............. "640"

Hi ,
You can increase the roll area and see if this problem persists.
The parameter is ztta/roll_area .
Also , you can increase the Heap memory too (abap/heap_area_total).
But before increasing the meory , find out if there is any possibility to correct the program , by reducing the size ofthe internal table.
Regards,
Ponni.
from Eric Brunelle: begging for points is totally against forum rules. read them

Publications - Successful job run - View Log File

Hi everyone,
We have a growing number of Publication (based on Webi documents) that are scheduled and I want to report on Errors & Warnings.
When a Job Fails, I can use our Auditing universe and get visibility of the failure reason. When a Job is Successful but there are warning within the Log File - I don't know how to access this information bar manually having to check each Log file which is not feasible.
i.e. This snapshot of the History of a publication looks like all three publications were successful:
The actual jobs ran HOWEVER the one @ 10:00 shows a Warning when you dig into the Log file:
- There are no schedulable documents in the publication. (FBE60503)
2014-04-03 10:00:17,552 WARN [PublishingService:HandlerPool-61] BusinessObjects_PublicationAdminLog_Instance_1633706 - [Publication ID # 1633706] - Unable to find any distributable documents in scope batch
Notifications are of no use to me here, they flag a Successful job even though a warning exits and no documents were sent.
Do you know if you can access these Publication Admin Log xxxxxxxx files and generate reports on them?
Many thanks
Gill

Hi RC,
The issue is not the reports failing, the issue is around reporting on such failures.
Do you know if you can access these Publication Admin Log xxxxxxxx files and generate reports on them?
With thanks
Gill

Project Scheduling Logs

Hello Experts,
We have a requirement where we need complete log of rescheduling the project activity that means system should save the previous scheduling data as baseline, each time we reschedule that project. For example:
A project is scheduled in the start with proper relationship with six month of total period. After one month, activity dates are changed or some new activities are added. Complete project is rescheduled and dates are changed. Now the system should save the previous dates of all activities as a baseline and new dates to the activities should be assigned. It should happen each time we reschedule the project. In SAP standard system over writes the dates but does not save the previous dates.
Please guide in this regard that how can we meet this requirement. Thanking in advance.
Regards

Hi
In planning board you have this option,whenever you reschedule a project, it shows the previous date bar with a diffrent color and the rescheduled dates.But once saved and when you reopen the project, you cannot see the old dates.
Your expectation in the thread is that you want to have a history of the dates, whenever you reschedule the project.
The solution can be a combination of User status and a version profile for automic version creation for this user status.
In your case you can define two user status for the activity,
the first one(initial status) forbidding the rescheduling
the second one which permits reshedule
So whenver the user want to reschedule, he has to go to the second status before rescheduling.
Create a version profile which versions the project automatically in this second status.
But I am afraid of a disadvantage out here,the user should set the status back to first one after rescheduling.To avoid this you can try out some enhancement which sets the status back to first one whenever you exit the project.
Regards
Ravi

Error while adding a job to scheduler

Hello,
I have a batch job that is running fine in both DEV and QA environment. In DEV, I am able to schedule and run it daily. I created a similar schedule in QA environment using BODS Mgmt Console/Administrator. However, upon Activating the schedule, I am getting the following error message. Would someone know why would this error be thrown and steps to troubleshoot this error?
Thanks.
[Repository:AECON_DW_REPOSITORY Schedule:Daily_Run_QA Error:Error while adding a job to scheduler]
When contacting the server above exception was encountered, so it will be assumed the schedule is not active anymore.

Hi Rizwan Tahir ,
Delete the job server associated with the current batch job and recreate it.
Then try creating a new schedule using the new job server.
And take care that job server is created in QA environment.
Hope this should work.
Regards,

ORA-20211: Active job does not exist, cannot link to job record.

Getting the above error while executing OWB mapping in production environment.
Details of the error :
ORA-20211: Active job does not exist, cannot link to job record.
ORA-06512: at "RADRUN.WB_RT_MAPAUDIT", line 1278
ORA-06512: at "RADRUN.WB_RT_MAPAUDIT", line 2110
ORA-06512: at "RADSTG.MAP_STG_AIRCRAFT", line 2384
ORA-06512: at "RADSTG.MAP_STG_AIRCRAFT", line 2513
RADRUN -- runtime schema
RADSTG -- Target schema where mappings deployed.
source database is accessed through a DB link.
OWB version - 10.1.0.4.0
Oracle - 9.2.0.6.0
Here mappings are getting executed by calling a pl/sql procedure. This pl/sql procedure is executed every day by scheduling a dbms_job. After the error, the job is in hanging.
Last week also the same error happened, on that occasion , restarted the database and re submitted the job. Mapping executed without any error.
Looking for the expert comments

Hi.
See Note:125860.1 in metalink (and please, lol to solution #3). It applies to older OWB versions though... Are you using DBMS_JOB or OEM to run these mappings? If so, then the metalink note might be useful help.
Karesz, I believe if the source database was down, it would fail with an ORA-12XXX Error.
Regards,
Marcos

When a job is scheduled log cannot be seen

Similar Messages

Maybe you are looking for