DB13 - Schedule

Hi All,
We are unable to schedule the jobs in DB13. But we schedule
to an immediate option, jobs are running properly.
Can any one help.
Thanks in advance,
DVRK

Hi,
Can you please check whether operation modes on RZ04 are defined.If its ok fine.
Then please do the complete maintenance of the instance profile in RZ04 and once gain schedule the job.
TRansaction RZ20 -> SAP CCMS Monitor Templates -> System Configuration -> SID ->      System Configuration -> Instance Status ->
Review the Note 82655 - Instance not configured correctly
Hope this solves the issue
Thanks & Regards,
Pradeep Srigiri

Similar Messages

  • Error in DB13 scheduled backup

    Hi All,
    We schedule db13 backup in SAP on DB6 database (WIN2K3 OS) the backup is completing successfully but it was giving couple of errors in JobLog. Please find the error messages as follows
    "Action deleted in SDBAP at 20061129225959"
    "Job cancelled after system exception ERROR_MESSAGE"
    Can any one tell me is there any problem with this error. Or can i ignore if we ignore this error can we able to restore this backup file?
    Thanks in advance.....
    Eshwar B

    Hi Eshwar,
    This is a message related to jobs which have been scheduled periodically. If someone deletes such a periodic job in DB13, the job in SM37 is not deleted immediately but only gets an invalidation timestamp. If the invalidated job tries to start again in SM37, it fails with the error message you experienced.
    Normally you can ignore this, as long as DB13 itselfs shows correct results. You should not interprete the jobs in SM37 only.
    Depending on your SAP release there is a background job which cleans up such invalidated SM37 jobs
    Best regards
    Ralf

  • DB13 - Scheduled Update Statistics not run - Error

    Hello gurus,
    I´m faccing with an error in DB13, I scheduled Update statistics every day but it did not run due an error.
    I think this may resulted because an authorization problem.
    In /usr/sap is with this permissions:
    drwxr-xr-x  15 orad01 dba   4096 Oct 18 16:34 sap
    The /oracle/D01/sapcheck is with the following permissions:
    drwxr-xr-x  2 orad01 dba     4096 Nov 14 20:28 sapcheck
    Inside of sapcheck directory I can see the following files with permissions:
    -rw-r--r-- 1 orad01 dba       32262 Oct 14 13:16 ceeimamu.sta
    -rw-r--r-- 1 orad01 dba        2705 Oct 15 17:42 ceeisafo.sta
    -rw-r--r-- 1 orad01 dba        2705 Oct 15 17:50 ceeisazq.sta
    -rw-r--r-- 1 orad01 dba        1932 Oct 15 17:58 ceeisbie.sta
    -rw-r--r-- 1 orad01 dba        1791 Oct 15 22:16 ceeisyhm.sta
    -rw-r--r-- 1 orad01 dba        1931 Oct 15 22:24 ceeisyta.sta
    -rw-r--r-- 1 orad01 dba    19394261 Oct 15 23:45 ceeiszph.sta
    -rw-r--r-- 1 orad01 dba        1930 Nov  9 11:27 ceenjunx.sta
    -rw-r--r-- 1 orad01 dba        1790 Nov  9 11:38 ceenjvuv.sta
    -rw-r--r-- 1 orad01 dba      143103 Nov  9 11:40 ceenjwnr.sta
    -rw-r--r-- 1 d01adm sapsys      521 Nov 16 14:46 ceeosxxw.sta
    -rw-r--r-- 1 d01adm sapsys      521 Nov 16 14:49 ceeosydo.sta
    -rw-r--r-- 1 d01adm sapsys      521 Nov 16 14:54 ceeosyqi.sta
    -rw-r--r-- 1 d01adm sapsys      521 Nov 16 15:57 ceeotefd.sta
    -rw-r--r-- 1 orad01 dba       18530 Nov 16 16:27 ceeotgun.sta
    -rw-r--r-- 1 orad01 dba         996 Nov 16 16:27 connD01.log
    In DB13 at details error, it show the following statements:
    Job executado
    Etapa 001 executada (program.RSDBAJOB, variante &0000000000016, nome usuário XNSJAD)
    Execução do comando lógico BRCONNECT No host segoviad04
    Parâmetros: -u / -jid STATS20101123153214 -c -f stats -t ALL
    BR0801I BRCONNECT 7.20 (7)
    BR0301E SQL error -2133 at location BrOraThrEnable-1, SQL statement:
    'ENABLE THREADS'
    BR0806I End of BRCONNECT processing: ceeqbmqh.sta2010-11-23 15.32.15
    BR0280I BRCONNECT time stamp: 2010-11-23 15.32.15
    BR0804I BRCONNECT terminated with errors
    External program terminated with exit code 3
    BRCONNECT returned error status E
    Job encerrado
    Can you help me please!? I do not know how to solve this situation...
    Best regards,
    João Dimas - Portugal

    This wasn´t a new installation... this was a migration from windows/sql server to linux/oracle... and after that migration process I made an oracle upgrade to 11.2g and during this oracle upgrade we upgrade the BRtools to 7.20 version.
    I set up other job from DB13 (Verify database) and also it not ran well, it show an error too, but a diferent one:
    Parameters:-u / -jid VERIF20101110030000 -c force -w only_dbv -p initD01.sap -m ALL
    BR0051I BRBACKUP 7.20 (7)
    BR0055I Start of database backup: beeqitms.dbv 2010-11-25 03.00.06
    BR0484I BRBACKUP log file: /oracle/D01/sapbackup/beeqitms.dbv
    BR0477I Oracle pfile /oracle/D01/112_64/dbs/initD01.ora created from spfile /oracle/D01/112_64/dbs/spfileD01.ora
    BR0068E SAP system is running or SAP user is connected to database D01 - database cannot be shut down
    BR1025I Please shut down SAP system first or use the 'offline_force' option
    BR0056I End of database backup: beeqitms.dbv 2010-11-25 03.00.09
    BR0280I BRBACKUP time stamp: 2010-11-25 03.00.09
    BR0054I BRBACKUP terminated with errors
    External program terminated with exit code 3
    BRBACKUP returned error status E
    I also checked the permissions in /usr/sap folder and sub folders as per the link you put here... and everything is well... but tell me one thing which owner/group must have set in /usr/sap/ directory? In that help sap link it doesn´t show any suggestion in this column, so I don´t know in this case which owner and group must have set... In my case the /usr/sap/ and dba as group:
    drwxr-xr-x 28 orad01 dba      4096 Nov 23 15:20 D01
    Kind regards,
    João Dimas - Portugal

  • DB13 scheduling problem

    Hi,
    We are unable to schedule the jobs in DB13 with the error SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error:
    We have a cluster setup where DB is running on one node and the application server on the other node.
    Now as per the snote: 446712 we need to have eithe RSH or any other tool.
    Is this RSH comes by default in windows 2003 or do we need install it seperately ? Please advise on other alternative ways
    to this issue.
    Thanks & Regards,
    DVRK

    Hi DVRK,
    There are no issues as such installing a gateway instance on the Database Instance. Two things which you might need to take care are
    1. Include the gateway start command in the os user profile or startsap script so that if you restart the DB instance, the gateway instance starts automatically.
    2. If the DB instance is on cluster, then include the gateway service and mount points to switchover using the cluster software.
    Apart from these two, i do not see any issues as such.
    Cheeers...,
    Raghu

  • DB13 scheduled tasks on java databases

    Hi,
    There are a possibility to connect to an ABAP system one java system for to schedule tasks over DB13?
    More thanks

    Yes.
    Check
    Note 1027512 - MSSQL: DBA cockpit for basis release 7.00 and later
    Markus

  • DB13 scheduled tasks not appear

    Hi people,
    I´ve connected an external Oracle databases, and I´ve scheduled some maintenance tasks.
    During on time, the finished and scheduled tasks appears in the DB13, but I´ve seen that the scheduled tasks off external databases not appear, but the time if scheduled tasks has passed, the tasks it´s correctly finished and appears.
    The problem is that the scheduled tasks cannot edit them, because not appears in the calendar, only when they´ve finished.
    What can i do?

    >> Regarding Note 6 in Note1025707, this is for if both systems are on the same server, for example, a server has AS ABAP CEN with DBA Cockpit and has AS Java JAV. Is this your situation? The Oracle DB for the separate AS Java would still be considered "remote" in this case. I do not have experience with this situation.
    For the instance, if the installation is a SAP Portal system, it is evaluated by a remote database, when you are attached it to a central monitoring system. For example you have two or more SAP installations even on a same physical host attached to the central monitoring system, those systems are evaluated as remote systems. This is because central monitoring system should be connected to these systems by remote.
    I hope that I clarified the issue.
    Best regards,
    Orkun Gedik

  • DB13 scheduled backups getting failed

    Hello Experts,
    Till sometime back our backups were working fine. But recently it started getting failed.
    I have checked the RFC connection SAPXPG_DBDEST_PRODORADB. RFC connection test is throwing the following error.
    Logon Connection Error
    Error Details Error when opening an RFC connection
    Error Details ERROR: timeout during allocate
    Error Details LOCATION: SAP-Gateway on host PRDAPP1 / sapgw00
    Error Details DETAIL: no connect of TP sapxpg from host PRODORADB
    after 20 sec
    Error Details COMPONENT: SAP-Gateway
    Error Details COUNTER: 217995
    Error Details MODULE: gwr3cpic.c
    Error Details LINE: 2030
    Error Details RETURN CODE: 242
    Error Details SUBRC: 0
    Error Details RELEASE: 700
    Error Details TIME: Thu Aug 4 12:34:49 2011
    Error Details VERSION: 2
    Please let me know how can I rectify the issue.
    Thanks & Regards,
    Shanahas.K

    Hi,
    You need to check whether service in port 123 is up.In the folder /etc/services you can see the entry
    For telnet aix use port number 123.Port number are mentioned in /etc/services file.check for available port in services file. and
    Check the user you telnet own the privilege of remote login or not
    Let me know
    Regards
    Thomas

  • Offline backup failing when scheduled using DB13

    Hi,
               We have done our backup schedule of our BI 7 system running on AIX 5.3 and Oracle 10.2 using DB13.The activities like online backup and datbase check is executing correctly but offline backup is failing with status unknown.
    If i check in sm37 for the DBA job offline backup is showing status completed successfully but in brbackup logs there is no log for the offline backup activity.
    Kindly provide your suggestion on how i can resolve this issue.

    Hi Ammey,
                   Thanks for your reply.
    When I trigger the backup directly from brtools offline backup is happening successfully.The issue is happening only for the db13 scheduled offline backup.The same thing happened for Update statistics but check db is executed.
    So what has to be checked in backint settings pls provide you suggestion.
    rgds,
    vinayak

  • Cleanup of DB13 Plannings + Job error

    Hi all,
    when i have gone through ST04, JOBS->DBA LOG, i am getting the following job  error
    16.01.2008     14:00:46     16.01.2008     14:00:46     00:00:00     Collection of DB Performance History     OK
    16.01.2008     14:00:44     16.01.2008     14:00:46     00:00:02     Cleanup of DB13 Plannings     Job error
    16.01.2008     13:00:44     16.01.2008     13:00:45     00:00:01     Collection of DB/DBM Config. History     OK
    16.01.2008     12:00:45     16.01.2008     12:00:45     00:00:00     Collection of DB Performance History     OK
    16.01.2008     12:00:43     16.01.2008     12:00:45     00:00:02     Cleanup of DB13 Plannings     Job error
    Actually what is this error ? Why it is caused? what is the solution
    regards
    padma

    The following note should be helpful ~
    [Note 576752 - DB6: Error in job for clear DB13 scheduling|https://service.sap.com/sap/support/notes/576752]

  • SQL error -1017 at location BrDbConnect-2, SQL statement:

    Hi,
      I get follwoing error while trying brarchiev.
      How do i fix this ?
    brarchive
    BR0002I BRARCHIVE 7.00 (18)
    BR0252E Function fopen() failed for '/oracle/XID/saparch/adyveabv.sve' at location main-5
    BR0253E errno 13: Permission denied
    BR0121E Processing of log file /oracle/XID/saparch/adyveabv.sve failed
    BR0280I BRARCHIVE time stamp: 2008-09-16 20.13.19
    BR0301W SQL error -1017 at location BrDbConnect-2, SQL statement:
    'CONNECT system/*******'
    ORA-01017: invalid username/password; logon denied
    BR0310W Connect to database instance XID failed
    BR0007I End of offline redo log processing: adyveabv.sve 2008-09-16 20.13.19
    BR0280I BRARCHIVE time stamp: 2008-09-16 20.13.19
    BR0005I BRARCHIVE terminated with errors
    3
    Thansk,
    Suman

    Hi,
    I think you did not specify any user on the command line, then BRCONNECT will use the default "SYSTEM/MANAGER"
    As you change the default, BR* fails.
    1) It is totally NOT recommended to use BR* from the command line, it is prefered to be used from the DB13 scheduling tool.
    2) you have to indicate to the BR* tool the user that has to be "used" to connect to the database. This is done with the parameter:
    -u <user>/<password>
    3) I recommend you to create the ops$<sid>adm user ( see note 361641 and 50088 ) and, if you do not use DB13, call the tool with thecommand
            brarchive -u / -s -p initBWP.sap.ssl2020.dd -c
    Please make sure that you have configured the OPS$ user correctly as per following notes:-
    400241    Problems with ops$ or sapr3 connect to Oracle
    50088    Creating OPS$ users on Windows NT/Oracle
    134592    Importing the SAPDBA role ( sapdba_role.sql)
    If the config of the OPS$ user is done correctly and follow the notes above,the issue will be resolved.
    Thanks & Regards,
    Pradeep Srigiri

  • Warning in CheckDB in Production server

    Dear All,
    I scheduled CheckDB in DB13, from last three days it is throwing warning. Please give me some solution for this. BRCONNECT Detail Log for Database is as:
    BR0973W Database operation alert - level: WARNING, operation: cdunacse.nxt, time: 2007-02-01 13.39.20, condition: Last successful 'nxt' operation older than 10 days
    BR0973W Database operation alert - level: WARNING, operation: sdtkglps.tbr, time: 2006-09-02 11.25.32, condition: Last 'tbr' operation failed with rc = 4
    BR0973W Database operation alert - level: WARNING, operation: 0607071128.rsi, time: 2006-07-07 11.29.00, condition: Last successful 'rsi' operation older than 10 days
    BR0973W Database operation alert - level: WARNING, operation: adsypacp.sve, time: 2006-07-02 17.57.07, condition: Last successful 'sve' operation older than 10 days
    BR0973W Database operation alert - level: WARNING, operation: cdsvhvsv.cln, time: 2006-06-15 10.08.29, condition: Last successful 'cln' operation older than 10 days
    BR0973W Database operation alert - level: WARNING, operation: sdsuygoa.dfa, time: 2006-06-13 11.21.00, condition: Last 'dfa' operation failed with rc = 2
    BR0973W Database operation alert - level: WARNING, operation: sdsuygkv.tse, time: 2006-06-13 11.19.37, condition: Last 'tse' operation failed with rc = 2
    BR0973W Database operation alert - level: WARNING, operation: sdsuyggr.dfa, time: 2006-06-13 11.17.49, condition: Last successful 'dfa' operation older than 10 days
    Thanks in advance

    BR0973W Database operation alert - level: WARNING, operation: cdunacse.nxt, time: 2007-02-01 13.39.20, condition: Last successful 'nxt' operation older than 10 days
    --> in DB13, schedule NEXTextents job
    BR0973W Database operation alert - level: WARNING, operation: sdtkglps.tbr, time: 2006-09-02 11.25.32, condition: Last 'tbr' operation failed with rc = 4
    --> last time you manipulated brtools, it ended with an error, check log sdtkglps.tbr
    BR0973W Database operation alert - level: WARNING, operation: 0607071128.rsi, time: 2006-07-07 11.29.00, condition: Last successful 'rsi' operation older than 10 days
    -->
    BR0973W Database operation alert - level: WARNING, operation: adsypacp.sve, time: 2006-07-02 17.57.07, condition: Last successful 'sve' operation older than 10 days
    --> run a brarchive run in DB13
    BR0973W Database operation alert - level: WARNING, operation: cdsvhvsv.cln, time: 2006-06-15 10.08.29, condition: Last successful 'cln' operation older than 10 days
    --> run a CLEANUP job in DB13
    BR0973W Database operation alert - level: WARNING, operation: sdsuygoa.dfa, time: 2006-06-13 11.21.00, condition: Last 'dfa' operation failed with rc = 2
    --> last time you manipulated brtools, it ended with an error, check log
    BR0973W Database operation alert - level: WARNING, operation: sdsuygkv.tse, time: 2006-06-13 11.19.37, condition: Last 'tse' operation failed with rc = 2
    --> last time you manipulated brtools, it ended with an error, check log
    BR0973W Database operation alert - level: WARNING, operation: sdsuyggr.dfa, time: 2006-06-13 11.17.49, condition: Last successful 'dfa' operation older than 10 days
    --> last time you manipulated brtools, it ended with an error, check log

  • What are the post instalation steps?

    hi,
    i am fresher in SAP.anybody plz send me postinstalation steps.
    regards,
    jana

    Hi All,
    Rewards if useful.
    Post Installation Steps For ECC 5.0
    What are the post installation steps after I have installed the Central Instance and Database instance?
    Initial Consistency Check
    SM28
    1.      Logon to the newly refreshed SAP system and run transaction SM28
    2.      Ensure that no errors are reported.  Otherwise, take the necessary steps to correct the problems.
    Edit Batch Jobs
    1.      Set the fields as follows
    Job name: RDDIMPDP*
    User name: *
    Job Status: Released and Ready checked off, all others unchecked
    Fr:  01/01/0001
    To:  12/31/9999
    Or after event: *
    2.      Press <F8> to execute the query
    3.      Highlight the first job in the list and press the <CTRL>+<F11> to change the job.
    4.      Examine the Exec Target field.
    a.      If the box is empty, press <F3> to exit
    b.      If the box is not empty, then clear out the contents so the field is blank and press <CTRL>+<S> to save
    5.      Repeat Steps 3 and 4 for each additonal job listed.
    Workbench Organizer Reconfiguration
    1.      Logon on to client 000 of the newly refreshed system with DDIC.
    SE06
    1.      Select the Database Copy or migration option
    2.      Press the Post-installation Processing button.
    3.      When prompted Do you want to re-install the CTS?, press the Yes button
    4.      When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected.  Press the checkmark button to continue.
    5.      When prompted Change originals from PRD to QUA?, press the Yes button
    6.      When prompted Delete TMS Configuration?, press the Yes button
    7.      When prompted Delete old TMS configuration?, press the Yes button
    8.      When prompted Delete Old Versions of transport routes?, press the No button
    TMS Configuration
    1.      Logon on to client 000 of the newly refreshed system.
    STMS
    1.      Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed
    2.      The information on this screen is automatically filled out from information provided during the SAP installation and should be correct.  If it correct, then enter a description for the system and press <CTRL>+S to save.  Otherwise, press the Other configuration button  and manually configure.
    3.      From the Overview menu, select Transport Routes
    4.      From the Configuration menu, select Adjust with Controller
    5.      Press the Yes button when prompted if you want copy the transport routes from the controller.
    Import Printers
    1.      Logon on to the production client of the newly refreshed system. 
    STMS
    2.      Press <F5> to go to the import Overview.
    3.      Double click on the <SID> of the newly refresh system
    4.      From the Extras menu select Other Requests, then Add.
    5.      In the Transp. Request box, enter the transport number containing the printer definitions that was exported.  Press <Enter> to save.
    6.      Select the transport that was just added to the queue and press <CTRL>+<F11> to start the import.
    7.      In the Target client box, enter the productive client of the newly created system.  Press <Enter> to save.
    8.      Press the <Yes> button to start the transport.
    Client Configuration
    SCC4
    1.      From the Table view menu, select Display -> Change
    2.      When warned that the table is cross-client, press the checkmark button.
    3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
    4.      Define client as follows:
    Client role:  Test
    Changes and transports for client-specific object:  Changes without automatic recording
    Client-independent object changes:  Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    5.      Press <CTRL>+S to save.
    6.      Repeat steps 4 through 6 for any additional clients
    Set System Change Option
    SE06
    1.      Press the System Change Option button.
    2.      Set the global setting to Modifiable
    3.      From the Edit menu, select Software Components Modifiable
    4.      From the Edit menu, select Namespaces Modifiable
    5.      Press <CTRL>+S to save.
    Import Users
    STMS
    1.      Press <F5> to go to the Import overview
    2.      Double click on the <SID> of the newly refreshed system.
    3.      Press <F5> to refresh the list of transports
    4.      Locate the transport in the list containing the user exports done before the start of the refresh.
    If the transport is NOT in the list, then from the Extras menu, select Other requests then Add.   Enter the transport number and press <Enter>.  Then press the Yes button to add the transport.
    5.      Highlight the transport and press the Import request icon .
    6.      At the client import screen, enter the target client and then press the Import button
    7.      Press <Enter> to confirm that the import will proceed
    SCC7
    1.      Run the Post Client Import Processing
    2.      The transport number should be the same as that of the transport started in STMS
    3.      Schedule the job to run in the background.  Do NOT schedule it to run immediately.  We need to modify the job before it can be released.
    4.      Press <CTRL>+S to save.
    SM37
    1.      Set the fields as follows
    Job name: CLIENTIMPORT*
    User name: *
    Job Status: All options checked
    Fr:  01/01/0001
    To:  12/31/9999
    Or after event: *
    2.      Highlight the job that was created by SCC7 and press <CTRL>+<F11> to modify the job.
    3.      Press the Step button.
    4.      Select the RSCLXCOP line and press <CTRL><SHIFT><F7> to modify that step.
    5.      In the User box, enter the background user for that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
    6.      Press <CTRL>+S to save the changes
    7.      Press <F3> to go back to the main job screen.
    8.      Press the Start condition button.
    9.      Press the Immediate button.
    10.     Press <CTRL>+S to save the changes
    11.     Press <CTRL>+S again to save all the changes to the job.
    12.     Job will start immediately once saved.  Press <F8> to refresh the list of jobs
    13.     Continue to press <F8> every once in a while to update the status of the job.  Do not continue until the job is completed sucessfully.
    SCC4
    1.      From the Table view menu, select Display -> Change
    2.      When warned that the table is cross-client, press the checkmark button.
    3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
    4.      Set the Protection to Protection level 1
    5.      Press <CTRL>+S to save.
    6.      Repeat steps 3 through 5 for any additional clients
    Deleting Source System Profiles
    RZ10
    1.      From the Utilities menu, select Import Profiles then Of Active Servers. 
    (Note:  All application servers of the target system must be started)
    2.      If the Display Profile Check Log screen is displayed, press <F3> to leave this screen.
    3.      Select the Profile field and press <F4> to bring up a list of profiles.
    4.      From the list select one of the profiles associated with the source production system.
    5.      From the Profile menu, select Delete, then All versions, then of a profile.
    6.      When prompted, press the Yes button to delete all version of the profile
    7.      When prompted to delete the file at the operating system level, press the No button.
    8.      Repeat steps 3 through 7 for all additional profiles associated with the source system
    Reconfigure Operation Modes
    RZ04
    1.      From the Operation Mode menu, select Timetable
    2.      Select Normal Operation and press the Change button.
    3.      Highlight 00:00 in the left hand column and press the Delete Assignment button
    4.      If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.
    5.      Once all the assignments are deleted, press <CTRL>+S to save.
    6.      If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.
    7.      Press <F3> to go back to the main RZ04 screen.
    8.      Right click on one of the listed Operation modes and select Delete
    9.      Press the Yes button to confirm the deletion.
    10.     Repeat steps 8 through 9 for any additional operation modes
    11.     Press <F5> to create a new operation mode.
    12.     Enter a name and short description for the operation mode
    13.     Press <CTRL>+S to save.
    14.     Press <F6> to create a new Instance
    15.     From the Settings menu, select Based on current settings, then New Instances, then Set
    16.     Press <F3> to go back to the main RZ04 screen.
    17.     Press the Yes button to save
    18.     From the Operation Mode menu, select Timetable
    19.     Select Normal Operation and press the Change button.
    20.     Highlight the 00:00 at the top and press <F2>
    21.     Highlight the 00:00 at the bottom and press <F2>
    22.     Press the Assign button.
    23.     Press <F4> to select the operation mode created above.
    24.     Press <CTRL>+S to save.
    Delete Update Failures
    SM13
    1.       Set the fields as follows
    Client:  *
    User: *
    From data: 01/01/0001
    From time: 00:00:00
    2.      Press <Enter> to display the list of outstanding update requests
    3.      If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing <F5> to select all records, then selecting the Update Records menu, then Delete.
    4.      Press the Continue button to confirm the deletion.
    Delete Batch Input Sessions
    SM35
    1.      From the Edit menu, select Select All
    2.      Press <Shift>+<F2> to delete all the batch input sessions.
    3.      Press the checkmark button to confirm
    4.      Press the Yes button to start the delete.
    Reorganize Spool
    SPAD
    1.      From the Administration menu select Clean-up Spool
    2.      Check all check boxes and enter 0 for minimum age
    3.      Press the Execute button
    4.      Once complete, press <F3> twice to get back to the main SPAD screen
    5.      From the Administration menu select Check Consistency
    6.      Press the Delete All button.
    SP12
    1.      From the TemSe database menu, select Consistency check
    2.      When the check is complete, press the Delete All button. 
    Delete Invalid Background Control Objects
    SM61
    1.      Press <F8> to switch in to change mode
    2.      Press the Cleanup List button.
    Restrict Outgoing Email and Faxes
    SCOT
    1.      Double click on the green Fax entry
    2.      From the Supported Address Types area, press the Set button that is beside Fax
    3.      In the Address area, ADJUST AS NECESSARY
    4.      Double click on the green SMTP entry
    5.      From the Supported Address Types area, press the Set button that is beside Internet
    6.      In the Address area, ADJUST AS NECESSARY
    Adjust RFC connections.
    SM59
    1.      Expand the TCP/IP connections section
    2.      Double click on the first entry listed
    3.      Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system.  
    Make changes as necessary.
    4.      Press the Test Connection button to test the connection
    5.      Press Press <CTRL>+S and then <F3> to save and return to the list of RFCs.
    6.      Repeat steps 1 through 5 for each additional RFC connection
    Convert Logical Systems
    Under no circumstances perform this procedure on a Production system
    BDLS
    1.      When warned to read the documentation, press the checkmark button.
    2.      In the Old logical system name box, press <F4>.
    3.      Select one of the production Logical System names that needs be changed (i.e. WIIPRD400)
    4.      In the New logical system name, enter what that logical system name should be called on this newly refreshed system (i.e.WIITRN400)   Note: Ignore Error/Warning about duplicate system by clicking on the check mark.
    5.      De-select the Test Run and Existence check on new names in tables options
    6.      From the Program menu, select Execute in background
    7.      Press the checkmark button when asked to select a spool device
    8.      Press the Immediate button when asked for the schedule
    9.      Press <Ctrl>+S to save
    10.     Use SM37 to monitor the job
    11.     When job is complete, repeat steps 2 through 10 for any additional logical system names that need to be changed.
    Adjust Logical Systems names
    SALE
    1.      Expand Sending and Receiving Systems, then Logical Systems
    2.      Click on the execute icon beside Define Logical System
    3.      Press the checkmark button to confirm that the change is cross client
    4.      …
    Allow Certains Settings to be modifiable
    (Refer to Note 356483 for more Details)
    SM54
    1.      Enter V_T001B in the Table/View box.
    2.      Select the Generated Objects option.
    3.      Press the Create/Change button.
    4.      Enter any access keys if requested
    5.      Change the Recording routine to no, or user, recording routine.
    6.      Press <Ctrl>+S to save
    7.      Press <Enter> if warned that you are changing a function group that doesn't belong to you.
    8.      You are prompted for transport.  Create a new local transport.
    9.      Repeat steps 1 through 8 for the following objects.  You can specify the same transport you created above.
    V_T001B_GL
    V_T093B_01
    V_T093B_02
    BSI Configuration (R3 HR Systems only)
    SM59
    1.      Expand TCP/IP Connections
    2.      Highlight BSI70-US-TAX and press the Change button
    3.      Change the program field to
    <hostname>\sapmnt\<SID>\SYS\EXE\RUN\TF60SERVER.EXE
    4.      Double check the target host and gateway point to the correct server
    5.      Press <CTRL>+S to save
    6.      Press the Test connection button to test.  If the connect is not successful, take the necessary steps to resolve the issue.
    SE38
    1.      In the Program field, enter RPUBTCU0
    2.      Press <F8> to execute
    3.      Select option BSI version 7.0
    4.      Press <F8> to execute
    5.      BSI should return tax calculations.  If there are errors, take the necessary steps to resolve.
    Reconfigure DB13 schedule
    DB13
    1.      Using the print out created before the refresh, recreate the DB13 calendar.
    Client Configuration
    SCC4
    1.      From the Table view menu, select Display -> Change
    2.      When warned that the table is cross-client, press the checkmark button.
    3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
    4.      Define clients as follows depending on client role
    Development
    Client role:  Customizing
    Changes and transports for client-specific object:  Automatic recording of changes
    Client-independent object changes:  Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    Quality Assurance
    Client role:  Test
    Changes and transports for client-specific object:  No changes allowed
    Client-independent object changes:  No Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    Training
    Client role:  Education
    Changes and transports for client-specific object:  No changes allowed
    Client-independent object changes:  No Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    Sandbox
    Client role:  Test
    Changes and transports for client-specific object:  Changes without automatic recording
    Client-independent object changes:  Changes to repository and cross-client customizing allowed
    Protection: Client copier and comparison tool:  Protection level 0
    Restrictions when starting CATT and eCATT:  eCATT and CATT allowed
    5.      Press <CTRL>+S to save.
    6.      Repeat steps 4 through 6 for any additional clients
    Set System Change Option
    Skip this section of the system is a Development or Sandbox System.
    SE06
    1.      Press the System Change Option button.
    2.      Set the global setting to Not Modifiable
    3.      Press <CTRL>+S to save.
    Release Background Jobs
    Currently, all background jobs, except for system standard jobs have been placed on hold (status scheduled).
    Rewards if useful.
    Regards,
    Pherasath

  • OIM11G db backup

    Hi All,
    Can anyone please help me to know which all schemas we should take the backup for the complete oim11g backup.I know soa,oim and mds.but I am missing one.
    If any one has the sql script/query to do so,please share.
    Thanks

    Hi Murali,
    One of the possibility might be, though the job is scheduled to run from DB13 but at the same time corresponding job is not present in SM37 or the user used for job scheduling is not valid of locked etc.
    So for the safer side as suggested by other users above, delete the same from DB13 and schedule fresh jobs.
    Make sure that the user, being used for DB13 scheduling is having enough authorization to run the job.
    It should work.
    Cheers !!!
    Ashish

  • DB backup not started

    Hi all,
    The DB backup scheduled through DB13 is not runnning .There is no log available for this.when you click the  date on which it is scheduled the status is showing as unknown.
    Kindly Provide your suggestions

    Hi Murali,
    One of the possibility might be, though the job is scheduled to run from DB13 but at the same time corresponding job is not present in SM37 or the user used for job scheduling is not valid of locked etc.
    So for the safer side as suggested by other users above, delete the same from DB13 and schedule fresh jobs.
    Make sure that the user, being used for DB13 scheduling is having enough authorization to run the job.
    It should work.
    Cheers !!!
    Ashish

  • Error while scheduling VerifyDB in DB13

    Hi,
    I am facing an error while scheduling VerifyDB through DB13 in my SAP ECC 6.0 system. This problem is occuring in the entire landscape(Dev, Quality & Prod) after i did an oracle upgrade from 10.1.0.4 to 10.2.0.2. The error is as below:
    BR1301W Error message from likeywlib:
    ===...could not load SSF library libsapsecu.so .
    BR1301W Error message from likeywlib: likey_init: Couldn't load SAPSECULIB ("libsapsecu.so") using function SsfSupInit (), rc = 10.
    BR1302E Initialization of license key library likeywlib failed, return code 1
    BR0602E No valid SAP license found - please contact SAP
    I also checked the note 912969 which gives the below solution:
    The error is corrected in BRSPACE 7.00 patch 10
    But the BRSPACE is already on a higher patchset (18). Patch 10 is already applied.
    Can somebody please guide me on this.
    Thanks & Regards,
    Smitha

    Hi Andreas,
       the error is exactly the same.
    The database is Oracle 10.2.0.2 and the backup is performed with a mix of BRtools and Legato.
    Any idea?
    Thanks
    Gianluca

Maybe you are looking for

  • Windows 7, no VoiceFX Changer?

    Windows 7, no VoiceFX Changer?I no longer have the tab to change my voice with the voice effects... cant find it anywhere in the control panel. Is this unique, or are many of you experiencing this as well? Other than that, I have the well documented

  • My MacBook Pro's hard drive is about full, can I move a lot of the data to my 3 TB Time Capsule?

    I have a late 2011 MacBook Pro 17 Inch with 750 GB of space on its hard drive.  About a month and half ago I bought a 3 TB Time Capsule and I know that Time Capsule, together with Time Machine, basically takes periodic snapshots of your hard drive an

  • IBook to iMac Slideshow

    I have a friend coming over with her iBook & was wondering if there was a quick way to hook her iBook up to my iMac to view a slideshow she has. Would you just do an ethernet to ethernet connection?

  • Web service to BW....Urgent!

    Hello experts I am trying to connect JDBC to SAP BW. I am getting a connection error. I checked in "Maintain services" using t-code SICF. default_host --> sap --> bw --> xml --> soap --> xmla. I checked all of the above components are active but stil

  • Not able to connect to RAC Database with VIP entries

    Hi All, My RAC database run with Physical Host entries in listener and tnsnames files. But VIP services are running in both nodes. Now i want to use VIP enties to connect to the RAC database from client side. I have modified the both the listener and