Oct 27
In extreme conditions you may want to copy a client using command line

Make a control file first
Quotation
netweaver:nw7adm 22> more clientcopy.ctl
clientcopy
source client = 001
target client = 130
select *


Then use R3trans to run with control file

Quotation
netweaver:nw7adm 19> R3trans -w clientcpy.log clientcopy.ctl
This is R3trans version 6.14 (release 700 - 16.10.08 - 16:26:00).
unicode enabled version
R3trans finished (0004).


The log file

Quotation
netweaver:nw7adm 9> more clientcpy.log
4 ETW000 R3trans version 6.14 (release 700 - 16.10.08 - 16:26:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 27.10.2010 - 20:59:22
4 ETW000 control file: clientcopy.ctl
4 ETW000 > clientcopy
4 ETW000 > source client = 001
4 ETW000 > target client = 130
4 ETW000 > select *
4 ETW000 R3trans was called as follows: R3trans -w clientcpy.log clientcopy.ctl
4 ETW000 Connected to DBMS = ORACLE --- dbs_ora_tnsname = 'CRM' --- SYSTEM = 'NW7'.
4 ETW690 COMMIT "0" "0"
4 ETW000  trace at level 1 opened for a given file pointer
4 ETW000
4 ETW000 ================== STEP 1 =====================
4 ETW000 date&time        : 27.10.2010 - 20:59:23
4 ETW000 function         : CLIENTCOPY
4 ETW000 buffersync       : YES
4 ETW000 from client      : 001
4 ETW000   to client      : 130
4 ETW000 l.s.m.           : VECTOR
4 ETW000 commit           : 100000
4 ETW000 table cache      : dynamic
4 ETW000
4 ETW000 Syslog: k CQ3 : UMGSETTING&                                          rscpexcc 12
4 ETW000 GetDBMigrateCodePagesLangs uses TCP0D, TCPDB, TCP0C.
4 ETW000   0 entries from /CRMMW/TST copied (001*).
4 ETW000   0 entries from /CRMMW/TST_CDB copied (001*).
4 ETW000   0 entries from /GC1/TCB_BUFF copied (001*).
4 ETW000   0 entries from /GC1/TSCOPE_BUFF copied (001*).
4 ETW000   0 entries from /GC1/TXXX copied (001*).
4 ETW000   0 entries from /OSP/T_AUDIT_USR copied (001*).
4 ETW000   0 entries from /OSP/T_BM_CTX copied (001*).
4 ETW000   0 entries from /OSP/T_BM_CTXT copied (001*).
4 ETW000   0 entries from /OSP/T_BM_RLV copied (001*).
4 ETW000   0 entries from /OSP/T_BM_RLVT copied (001*).
4 ETW000   0 entries from /OSP/T_CORRELATE copied (001*).
4 ETW000   0 entries from /OSP/T_CORR_EXT copied (001*).
4 ETW000   0 entries from /OSP/T_CORR_SAP copied (001*).
4 ETW000  62 entries from /OSP/T_GD_SETNG copied (001*).
4 ETW000 124 entries from /OSP/T_GD_SETNGT copied (001*).
4 ETW000 233 entries from /OSP/T_GD_VALUE copied (001*).
4 ETW690 COMMIT "131698" "131698"
4 ETW000 449 entries from /OSP/T_GD_VALUET copied (001*).
4 ETW690 COMMIT "322382" "454080"
4 ETW000   0 entries from /OSP/T_JOBINFO copied (001*).
4 ETW000   1 entry from /OSP/T_MDR_APPL copied (001*).
4 ETW000   0 entries from /OSP/T_MDR_APPLT copied (001*).
4 ETW000   5 entries from /OSP/T_MDR_SCN copied (001*).
Aug 17
While user tried to release a job from "scheduled status", an error showed 'You are not authorized to release background jobs".

Then do a 'SU53', the authorization object checked failed, which was 'S_BTCH_ADM',  and it need a value 'Y'. But as we know by giving such authorization it will be big security risk.

But actually if assign the user S_BTCH_JOB with JOBACTION = 'RELE', user is able to release job as well..

So sometimes SU53 might not tell the best answer...

Aug 7
If the access method M is not available, you must first run report RSPO0075 in transaction SE38, to activate the access method. It will then be available to you in transaction SPAD.

To do this, enter the name of the report in the Program field in transaction SE38, and choose This graphic is explained in the accompanying text Execute. Select the option Add Access Method, and choose the access method M as the access method to be added.

http://help.sap.com/saphelp_nw04/helpdata/en/ae/16193ce8fac413e10000000a114084/content.htm
Jun 30
After re-creating the control files for database, start the database only, leave the application server down.

1. Change the instance profile by setting the BTC working process number to 0.

2. Change all the released jobs to scheduled status.

Run sqlplus

select the table tbtco to see how many jobs are in 'released' status:

select * from tbtco where STATUS != 'P' and STATUS !='F' and SDLSTRTDT = $current_date

then try to update this table

3. Start the application server, then login to SAP

4. clean all the backup logs

5. clean all the spool TemSe by SP12

6. Run BDLS to convert the logical name.
Jun 16
1. Check table RSADMIN, confirm the entry BW_USER and SOURCESYSTEM_USER is not empty

2.Maintain the entry using the following path:

Call Administrator workbench (transaction RSA1).
From the 'Settings' menu, select Global Settings'.
If an entry already exists in the field "BW user for ALE", delete this.
Enter the correct names for the BW users in this field.
Save the entry.
You must restart the Administrator Workbench (RSA1) now.
The source system can now be linked without errors.
Pages: 1/4 First page 1 2 3 4 Next page Final page [ View by Articles | List ]