Posts filed under ‘Uncategorized’
Deleting SQL2005 Java Schema for SAP
declare @schema varchar(200)
select @schema = ‘SAPTRNDB’
select
‘DROP ‘ + case
when o.xtype = ‘U’ then ‘TABLE’
when o.xtype = ‘V’ then ‘VIEW’
when o.xtype = ‘P’ then ‘PROCEDURE’
when o.xtype = ‘FN’ then ‘FUNCTION’
end + ‘ ‘ + s.name + ‘.’ + o.name as SQL
from
sys.sysobjects as o
join sys.schemas as s on o.uid = s.schema_id
where
s.name = @schema and
o.xtype in (‘U’,’V’,’P’,’FN’)
union all
select
‘DROP SCHEMA ‘ + @schema
Adding text to the SAP logon screen
Go to Transaction SE61 and select the document ‘General text’, and create a text with the name ZLOGIN_SCREEN_INFO
Important SAP Notes on SQL Server
1076022: Release planning for Microsoft SQL Server 2008 (R2)
1152240: Setting Up Microsoft SQL Server 2008 (R2)
1144459: SQL4SAP and SAP Installation Media for SQL Server 2008
1473016: Service Pack Installation for SQL Server 2008
1279358: Cumulative Update Installation for SQL Server 2008
1260968: COPYTOSHADOW: R3trans loses reports
1237682: Configuration Parameters for SQL Server 2008
1600699: Microsoft jdbc driver 1.2 support
62988: Service Packs for Microsoft SQL Server
398136: Support Policy for Microsoft SQL Server
1177356: MS SQL Server: End of Support for SAP Releases
1027512: MSSQL: DBA cockpit for basis release 7.00 and later
683447: SAP Tools for MS SQL Server
1248222: ODBC DBSL profile parameters and connect options
208632: TCP/IP network protocol for MSSQL
128126: Database Connect for external tools
142731: DBCC checks of SQL Server
767691: Migration of SAP Systems to/from MS SQL Server
151603: Copying an SQL Server database
1086375: There is already an object named ‘..’ in the database
592514: MSSQL: internal database users, permissions and security
1294762: SCHEMA4SAP.VBS
1488135: Database compression for SQL Server
1459005: Enabling index compression for SQL Server
1238993: Proportional File Auto-Growth with SQL Server 2008
363018: File management for SQL Server
Database File Administration
32129: Deadlock analysis for the SQL server
Deadlocks
869407: Partitioning on MS SQL Server
1471910: SQL Server Partitioning in System Copies and DB Migrations
Table Partitioning (only relevant for SAP BW based systems)
965908: SQL Server Database Mirroring and SAP Applications
493290: Configuring SQL server Log shipping
High Availability
44449: Backup strategies with the SQL server
1297986: Backup and Restore strategy for MS SQL Server
1420452: FAQ: Restore and recovery with MS SQL Server
1048382: SQL Server: Third Party Backup Tool support
Backup and Recovery
1241751: SQL Server minimal logging extensions
1134345: Using locked pages for SQL Server
929031: Using SQL Server Profiler for JAVA (and ABAP)
159171: Recompilation of Stored Procedures
General Performance
129385: Database hints in Open SQL
133381: Database-Hints in Open SQL for MS SQL Server
1552952: Parameter maxmarkercnt increased to 10000
Performance -> Optimizer Hints
1380493: SQL Server Transparent Data Encryption (TDE)
Security
How to add/change/delete a printer:
Spool related:
How to add/change/delete a printer:
1)Add a Printer (Defining an R/3 printer device):
1. Log on to any client with your username and password in the SAP system.
2. Type SPAD in the command box on upper left corner and press enter key
3. It will take you on the Spool Administration screen: under the Devices/servers tab click the Output devices button.
4. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon to switch into change mode. The easiest way to create a new printer is to copy an existing one. Click on a similar printer in the output devices screen then click the create with template picture-icon.
5. On the Spool Administration: Create Output Device screen, fill in the Output device and Short name. Make any changes that are unique for the new printer on the Device Attributes and Host Spool Acc Method tabs. When all the required data has been changed/added, click the Save picture-icon.
6. You will receive an Output device was saved message in the status bar at the bottom of the screen. Click the lit match picture-icon to activate the printer
è T-code SPAD
Initial spool administration screen:
Click on Configuration à Output Devices:
SAVE again
2) Change a Printer:
- Go to transaction SPAD.
2. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button.
3. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon to switch into change mode. Double click on the output device to be changed.
4. On the Spool Administration: Output Device (Change) screen, make any necessary changes on the Device Attributes and Host Spool Acc Method tabs. When all the required data has been changed/added, click the Save picture-icon.
5. You will receive an Output device was saved message in the status bar at the bottom of the screen. Click the lit match picture-icon to activate the printer.
3) Delete a Printer:
1. Go to transaction SPAD.
2. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button.
3. On the Spool Administration: List of Output Devices screen, click the pencil picture-icon to switch into change mode. Click on the output device to be deleted and then click the trash can picture-icon.
4. On the Spool admin.: Delete screen, verify that the correct printer is about to be deleted. Click the Yes button.
5. You will receive an Output device deleted message in the status bar at the bottom of the screen.
T-code SPAD à Configuration-à Output Devices
2) How to reset the cache for a printer:
- Go to transaction SPAD.
2. On the Spool Administration: Initial Screen screen, under the Devices/servers tab click the Output devices button.
3. On the Spool Administration: List of Output Devices screen, double click on the printer you need to reset.
4. On the Spool Administration: Output Device (Display) screen, click on the pencil picture-icon to switch from display mode to change mode.
5. On the same Administration: Output Device (Display) screen, on the top-most menu bar click Edit → Reset Cache.
6. On the Administration: Output Device (Change) screen, on the top-most menu bar click Edit → Reactivate.
7. On the same Administration: Output Device (Display) screen, on the top-most menu bar click Edit → NI Reset.
3) How to reprint and reroute print:
Reprint:
1. Go to transaction SP01.
2. On the Output Controller: Spool request selection Screen screen, fill in any information needed to filter the selection results. Then click on the clock picture-icon.
3. A list of all spool requests will be displayed. Double click on the spool request that is to be reprinted.
4. Click on the printer picture-icon. An Output request created message should appear in the bottom status bar.
à If it is front-end printing, the below screen appears when you print:
Reroute Print:
1. Go to transaction SP01.
2. On the Output Controller: Spool request selection Screen screen, fill in any information needed to filter the selection results. Then click on the clock picture-icon.
3. A list of all spool requests will be displayed. Double click on the spool request that is to be reprinted.
4. Click on the printer with a box outline picture-icon. On the Output controller: Print spool request XXXX screen, tab down to the line reading Output device and select a new printer. Click on the printer picture-icon.
5. On the Output control: Save attributes popup, click the Yes button.
6. On the Confirm redirection of output popup, click the Yes button. An Output request created message should appear in the bottom status bar.
Double click the spool no, you want to print
The below screen appears:
Print successfully.
How to reorganize and reclaim TemSe objects:
1. Go to transaction SP12.
2. On the TemSe — Administration of Temporary Sequential Data screen, on the top-most menu bar click TemSe database → Reorganization.
3. On the TemSe — Administration of Temporary Sequential Data popup, click the All TemSe objects older than option to turn “on” the radio button to the left. Fill in the Days box with “7” for development and quality assurances SAP systems, and “32” in production SAP systems. Click the Delete button.
4. On the TemSe objects older than XX days popup, click the Yes button.
5. After the successful deletion of the selected temporary objects, you will be returned to the TemSe — Administration of
Temporary Sequential Data screen. There is no task completion message.
How to keep the job log clean:
1. Go to transaction SE38 and type in Program name RSBTCDEL and click on the Execute button.
2. On the Delete batch jobs screen, fill in the filtering information you need. It is suggested that Delete with forced mode be “on”. Click on the Execute button.
3. A status message will appear in the bottom Status Bar as the list of job logs to be deleted is built. Once all the specified job logs have been deleted, a final total of jobs logs cleaned will appear in the bottom Status Bar.
________________________________________________________________
BI Transports source system issue
While moving Transports from BI Dev to Bi QA will get error SOURCE SYSTEM DOES NOT EXISTS, to avoid this error configure
TCODE: RSA1
Goto Tools and select Conversion of logical system names or press CTRL+F12
Give Original Source system, Target Source System
Restoring Database PRD to QAS homogenous
In quality all the file systems must be in same size as production system
After installation of SAP in quality
Take the offline / online backup of production system using db13
Connect the tape drive / backup drive to quality system
Check the drive using: brbackup –I show –n 1
Copy the backup log file from prod to quality
Eg: in prod
/oracle/<sid>/sapbackup/abcd.afp file
To QAS
/oracle/<sid>/sapbackup/abcd.afp
&
Copy back<sid>.log file from production quality to /oracle/<sid>/sapbackup/backsid.log
Modify the .afp file from old sid to new sid eg: HPS to HQS except at volume_backup, Following backup volume will be used, Volume with name HPSB15 required in device.
In quality system run the following command in orasid user name
brrestore –b <modified backuplogfile> -m FULL
After completion of restoring generate control file in production system using
Sqlplus “/as sysdba”
Sql> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
Copy that trace file from production /oracle/sid/saptrace/usertrace/*.trc (latest file) to qulity
Modify the trace file
Delete the lines before STARTUP NOMOUNT and after CHARACTER SET UTF8;
And modify old <sid> to new <sid> in all the lines
Modify the line after startup nomount as
CREATE CONTROLFILE SET DATABASE “SID” RESETLOGS FORCE LOGGING ARCHIVELOG
Rename the file to contrl.sql and place it in /oracle/sid/saptrace/usertrace/
Rename the cntrlsid.dbf files to old_cntrlsid.dbf in the following locations in quality
/oracle/sid/sapdata1/cntrl/
/oracle/sid/origlogA/cntrl/
/oracle/sid/origlogB/cntrl/
Any other places with cntrl folder
Run the contrl.sql from /oracle/sid/saptrace/usertrace
Sqlplus “/as sysdba”
Sql> shutdown immediate;
Sql> @contrl.sql
After successful creation of control file.
Sql> ALTER DATABASE OPEN RESETLOGS;
Now database must be in open
You need to create the users
OPS$ORA<newsid>
OPS$SAPSERVICE<newsid>
OPS$<newsid>ADM in database with same authorizations of old sid users.
Now check the connectivity using r3trans –d if successful you can start sap.
Note: It works only in homogenous environments if its heterogeneous then use systemcopy method
Procedure to get SAP CERTIFIED TECHNOLOGY ASSOCIATE – SYSTEM ADMINISTRATION
Phani Kumar's Blog for Basis 