Log on to the CUA central system for eg DE2 050 or EE2 050 and then run the report in SE38
RSDELCUA
then choose the system that you need to disconnect and then resynchronize.
Thursday, July 15, 2010
Tuesday, July 13, 2010
GRC Java System Info has different link
When clicked on System Info link for SAP GRC 5.3 system (AS JAVA) took us to the below standard link :
http://server:port/monitoring/SystemInfo
but it gave us the below error :
Requested Resource [/SystemInfo] not found.
changed the above link to the following and it worked
http://server:port/sap/monitoring/SystemInfo
http://server:port/monitoring/SystemInfo
but it gave us the below error :
Requested Resource [/SystemInfo] not found.
changed the above link to the following and it worked
http://server:port/sap/monitoring/SystemInfo
Sunday, July 11, 2010
SAP Note 1086644 Pcd clean Inconsistencies in Portal
We can run PcdToolCheck.sh to check and clean Pcd Inconsistencies.
Thursday, July 8, 2010
Gyan Session on MDM
The primary function of MDM includes:
Master Data Consolidation
- cleansing and de-duplication
- Data normalization including categorization and taxonomy mgt
- New interactive consolidation capabilities
T-Code to upload data in MDM through ECC MDMGX
There is a Ready folder that acts as a source for data staging
There are three important modules:
CI - MDS
App Server - Import Server - for input to MDM
App Server - Syndicate Server - for sending out data from MDM
The analogy for CI and App is only for shutting down and startup.
Master Data Consolidation
- cleansing and de-duplication
- Data normalization including categorization and taxonomy mgt
- New interactive consolidation capabilities
T-Code to upload data in MDM through ECC MDMGX
There is a Ready folder that acts as a source for data staging
There are three important modules:
CI - MDS
App Server - Import Server - for input to MDM
App Server - Syndicate Server - for sending out data from MDM
The analogy for CI and App is only for shutting down and startup.
Wednesday, July 7, 2010
Operation Mode Simulation Errors
Sometimes the Operation Mode switching is not consistent. The number of Work processes shown in the RZ04 doesn't match with the actual work processes. Please follow the same to correct it :
Goto RZ03 -) Control -) Switch Operation Mode -) Simulation
If it is giving errors then you need to fix the same
Goto RZ04 -) Double click on any operation Mode -) Goto Settings -) Based on current status -) Existing Instances -) Set
now check the above step of RZ03 it should be green now and now you may actually switch operation modes in RZ03 Control tab and the WPs should match now.
Time Table TCode SM63
Goto RZ03 -) Control -) Switch Operation Mode -) Simulation
If it is giving errors then you need to fix the same
Goto RZ04 -) Double click on any operation Mode -) Goto Settings -) Based on current status -) Existing Instances -) Set
now check the above step of RZ03 it should be green now and now you may actually switch operation modes in RZ03 Control tab and the WPs should match now.
Time Table TCode SM63
Saturday, July 3, 2010
IDoc monitoring and manual Parallel Processing
We can monitor IDocs using T-code WE05
In current status put 64 (IDocs ready to be transferred to an application)
There you may see the IDocs with large segments that are stuck, make a note of their numbers
Go to SA38 and execute the program RBDAPP01
Give the IDoc number only and click on Program -) execute in background and select immediate
You may run many jobs parallely for the same when the job finishes it means the IDoc is processed.
In current status put 64 (IDocs ready to be transferred to an application)
There you may see the IDocs with large segments that are stuck, make a note of their numbers
Go to SA38 and execute the program RBDAPP01
Give the IDoc number only and click on Program -) execute in background and select immediate
You may run many jobs parallely for the same when the job finishes it means the IDoc is processed.
Database Shutdown Process - Oracle
1. Connect to O/S (UNIX) using ora(SID)
2. Connect database #sqlplus "/as sysdba"
3. Check database name and database open mode
SQL) select name, open_mode from v$database;
4. Check database backup status using following command
SQL) select * from v$backup;
If status in not active then you may shutdown database using command
SQL) shutdown immediate
If status is active state then first cancel backup using command
SQL) alter database end backup;
after successful execution of this command database can be shutdown using command
SQL ) shutdown immediate;
5. Check any backint process in O/S level using command
$ps -ef grep backint grep ora(SID)
6. If there exists any process kill using following command
#kill -9 (PID)
2. Connect database #sqlplus "/as sysdba"
3. Check database name and database open mode
SQL) select name, open_mode from v$database;
4. Check database backup status using following command
SQL) select * from v$backup;
If status in not active then you may shutdown database using command
SQL) shutdown immediate
If status is active state then first cancel backup using command
SQL) alter database end backup;
after successful execution of this command database can be shutdown using command
SQL ) shutdown immediate;
5. Check any backint process in O/S level using command
$ps -ef grep backint grep ora(SID)
6. If there exists any process kill using following command
#kill -9 (PID)
Subscribe to:
Posts (Atom)