How can we calculate archivelog size each day/hour?
This is not a difficult idea for someone who work as DBA, I just wish more idea for discussion and sharing . Some Idea using V$LOG.BYTES and V$ARCHIVED_LOG.*
but I believe V$ARCHIVED_LOG view be able to help:
Archivelog size each day:
SQL> select trunc(COMPLETION_TIME) TIME, SUM(BLOCKS * BLOCK_SIZE)/1024/1024 SIZE_MB from V$ARCHIVED_LOG group by trunc (COMPLETION_TIME) order by 1;
Archivelog size each hour:
SQL> alter session set nls_date_format = ‘YYYY-MM-DD HH24’;
Session altered. (more…)
Lately, I am facing some error “LIST_TOO_MANY_LPROS” when using SAPGUI for Java 7.20 rev 9 to access SAP ERP 6.0 EHp 5 with Basis release 702 SP 12 (KB70212). Then I search this on service.sap.com and found this useful SAP Notes 17447011.
Accessing Implementation Guide through SPRO in HTML & JAVA GUI results in Runtime error as LIST_TOO_MANY_LPROS
Reason and Prerequisites
While accessing IMG through SPRO in HTML & JAVA GUI, it results into run time error as LIST_TOO_MANY_LPROS.
This is because of some method calls are failing to be implimented in JAVA and HTML GUI.
Manual Steps to be followed:
1. Enter T-Code ‘SPRO’.
2. Click on ‘Settings’..’User-Specific Settings’..’General’
3. Uncheck all the check boxes.
4. Restart the t-code ‘SPRO’.
By this, some of the Control features cannot be accessed,
but the IMG navigation is possible.
Now, I am able to access SPRO smoothly again.
Hope the below information helps.
HOW to do remote client copy ( SCC8 )
1. create the new client in the target system via tcode SCC4
2. log on to the traget client of the traget system with the user SAP* and password PASS
3. for the planned copy run, you must define the RFC connection between the R3 systems as the source client, if this has not already been
4. you should also protect the source client of the source system against changes during the copy. To do this, log on to the source system and
lock the source client : In scc4 (
change mode ), choose the option ” Currently locked Due to client Copy ”
5. you can start the copy in the target system. Execute tcode SCC9
6. using the profile, choose the data to be copied
7. choose the RFC connection. The source system and client are chosen automatically for the RFC connection
8. before the actual copy, test the RFC connection using the RFC system check. In addition to testing the connection, the R3 system releases
9. start the copy in background ( in test mode )
10. check the status of the copy procedure from the target system. You can do this at any time by choosing Client Administration..tcode SCC3
11. start the copy in background ( in final mode )
12. check the status of the copy procedure…SCC3
NOTE : with a remote client copy, only the table data is moved, not the table definitions. If user-specific, client-dependent tables were created in
the source client, they are not automatically copied to the target client, and an error may be caused. It is the responsibility of the user to create
the necessary tables in the target client manually via SE11.
HOW to do client transport : ( SCC9 )
prerequisites : the source and target system must have the same R3 release. The R3 system can not checked the R3 release since there is no
connection between the
1. create the target client in the target system via tcode SCC4
2. log on the source client in the source system with a user with transport authorization ( Not SAP* or DDIC )
3. using the client maintenance tool ( SCC4 ), lock the source client against changes
4. go to the client transport menu by choosing Tools > Administration > Administration > Client Transport > Client Export or transaction SCC9.
When you confirm your
selection, you are notified of which transport requests were created for this task.
KO – Client-independent
KT – client-dependent
KX – texts
5. check the logs created for the copy run via SCC3
To import the transports created into another R3 system :
1. copy the required files to the corresponding subdirectory of the local transport directory of the target system
2. on the operating system level, from the subdirectory bin of the local transport directory of the target system, execute the commands :
tp addtobuffer <request> <target system> client=<client>
tp import <request> <target system> client=<client>
3. the remaining file with the text elements requires different procedure. Log on to the target client of the target system and access the client
administration tool by selecting
Tools > Administration > Client Administration > Client Admin. Choose client Transport > Post-process Import. Select the request
<SID>KT<number of the request> and
execute it online or in background. This procedure copies and generates the client-dependent text elements.
With Version SAP_BASIS 702 a new feature was added to the TMS system, tp was checking the component version of the transport which was released and the component version of the system where the transport was going to be imported. If there was a difference, this difference was highlighted in the import queue (transaction stms_import) and if you tried to import the transport, the import would stop with a warning message about the difference in the SAPCOMPONENT versions.
You have error import status “Request does not match component version”.
Set STMS profile parameter : SP_TRANS_SYNC = OFF
This can be added via transaction STMS of the domain controller.
Call transaction STMS
Goto ‘Systems Overview’
Double click you wish to add the parameter to
Goto ‘Transport Tool’ tab
Goto ‘change mode’
Add SP_TRANS_SYNC to parameter column and OFF to value column
Save, activate and distribute
Related SAP Notes
1581638 SAP component checks no longer working in TMS
1577714 Transport requests in Check requirements phase