PA20 and PA30 tcode execution is very slow

There was an issue in our Project some users were facing extraordinarily long response times while using transactions PA20 and PA30, the resolution was as follows:

Do you happen to have structural authorization implemented ? If yes, this can cause performance issue when doing authrorization checking. To resolve this (only if you have struct auth implemented) , the user id would need to be added in T77UU, and SAP utility to re-generate index for structural auth (RHBAUS00) to be run after .

Source : https://forums.sdn.sap.com/thread.jspa?threadID=1458192

Oracle Schema User Locked in trans.log ORA-28000

951167- ORA-28000: the account is locked

Problem
You cannot log on to the Oracle database and the program returns the message:

ORA-28000: the account is locked



Reason and Prerequisites

ORA-28000 is usually triggered because someone has previously attempted to log on several times using an incorrect password, which causes the logon to fail and returns ORA-01017. The number of allowed logon attempts is defined by the resource FAILED_LOGIN_ATTEMPTS in the profile. You can determine the current value of this parameter using the following query:

SELECT LIMIT FROM DBA_PROFILES
WHERE
PROFILE = 'DEFAULT' AND
RESOURCE_NAME = 'FAILED_LOGIN_ATTEMPTS';

Until Oracle 10.1, this parameter had the default value UNLIMITED, so that no ORA-28000 messages would normally occur. As of Oracle 10.2, this standard value has been set to 10.

A further option in the case of a locked user is an explicit lock as follows:

ALTER USER ACCOUNT LOCK;


Solution

To prevent ORA-28000 errors, and avoid similar problems in future, be aware of the following:

If you use Oracle 9i or earlier, do not manually restrict the authorizations of the default profile (also refer to Note 700548 (16)).
If FAILED_LOGIN_ATTEMPTS is not set to UNLIMITED, you can adjust it as follows:

ALTER PROFILE DEFAULT LIMIT FAILED_LOGIN_ATTEMPTS UNLIMITED;
This is also possible for Oracle 10. 1 and earlier and Oracle 10.2 and later.

If a user is already locked, you can unlock it as follows:

ALTER USER ACCOUNT UNLOCK;
If the ORA-28000 error occurred due to a large number of failed logon attempts, you must check why these logon attempts were unsuccessful and returned the ORA-01017 error. The cause is often an incorrect configuration of the OPS$ mechanism. In this case, refer to Note 400241.

Why is it necessary to delete the tables ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAP, SDBAR, TPFET, and TPHFT in an SAP System Refresh

Those tables contain information specific to the source system. On the target system this piece of information will be misleading or wrong.


Tables SDBAD, SDBAP, SDBAR are about backup history. Backups of the source system won't tell you anything about backups of the target system.

TPFET and TPHFT are about SAP instance profiles. You can't keep profiles of the source system; you will have to create new ones for the target system anyway.


Below tables:

SDBAP = SAP DBA Plan Table
SDBAR = SDBA Resource Table
SDBAH = Header table for DBA protocols
SDBAD = Detail table for DBA protocols

belong to sapdba. They contain the log information of the logs that
sapdba and BrBackup and BrArchive write. The sapdba -cleanup function
will enable you to delete the entries from the db-tables, as well as the
respective files in the operating system.

The tables
MONI = Monitor table
PAHI = History of OS system, DB and SAP parameters
ALAMO = Collector of alert events
OSMON = Operating system monitor data
DBSNP = Table for DB snapshots

contain statistical data tha can be displayed in transaction st04. They
can partially be deleted from within the R/3-System following
st04->Monitor->Performance->Database

Tables:
ALSYSTEMS:CCMS Central System Management: Remote Managed Systems

As they contain information related to that source system and will be misleading if copied to target system.

They can partially be deleted from within the R/3-System following
st04->Monitor->Performance->Database

If not work, you can truncate these tables with sqlplus.

sqlplus sapr3/sap
truncate table ;

There is another option to delete all the data with SE14, using database
utility.

Source : https://forums.sdn.sap.com/thread.jspa?threadID=1204044

Disconnecting System from CUA

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.

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

SAP Note 1086644 Pcd clean Inconsistencies in Portal

We can run PcdToolCheck.sh to check and clean Pcd Inconsistencies.

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.

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

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.

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)