SAP note 1394553 - EH&S WWI server installation instructions
Transactions:
CGSADM - Administer connections
CG5Z - WWI monitor (make servers active)
Customising Configuration:
SPRO
-> SAP Reference IMG
-> Environment, Health and Safety
-> Basic Data and Tools
-> Report Definition
-> Windows Wordprocessor Integration (WWI)
-> Configuration of Generation Servers
-> Manual Configuration of Generation Servers
-> Specify Generation Servers
Allows direct editing of table TCGS8
Tables:
TCGS1 - EHS: WWI spool cluster Spool dest. <->->
TCGS2 - EHS: Assignment EHS doc. cat. < > DMS doc.
TCGS3 - EHS: WWI destinations
TCGS4 - EHS: Language-Dependent Description for WWI destinations
TCGS5 - EHS: Assignment of WWI destinations to PCs used for gen.
TCGS6 - EHS: Definition of WWI printer types
TCGS7 - EHS: Language-Dependent Description for WWI printer types
TCGS8 - EHS: Definition of PCs used for WWI document generation
TCGS9 - EHS: Language-Dependent Description for WWI generation PCs
TCGSGP - EHS: Search parameter (reproduction from SET/GET memory)
TCGST01 - EHS: Control Table for EH&S Status
TCGST02 - EHS: Assignment Value Assignment Type to Status
Thursday, 1 October 2015
Monday, 28 September 2015
Adjust Stack.xml file
To adjust the content of a stack.xml file to change the system name:
Run transaction SE38
Enter program name RPT_MOPZ_COPY_STACK_XML
See SAP note 1600302 - MOpz: Copy stack xml with a report
Run transaction SE38
Enter program name RPT_MOPZ_COPY_STACK_XML
See SAP note 1600302 - MOpz: Copy stack xml with a report
Wednesday, 16 September 2015
DB2: Restart db2vend process
If the db2vend process needs to be restarted using "kill -9 <PID>" could crash the database.
IBM's recommendation is to run the following command:
db2pd -db <dbname> -fvp lam1 term
(where "lam1" stands for LOGARCHMETH1)
See here (http://www-01.ibm.com/support/docview.wss?uid=swg21607001)
IBM's recommendation is to run the following command:
db2pd -db <dbname> -fvp lam1 term
(where "lam1" stands for LOGARCHMETH1)
See here (http://www-01.ibm.com/support/docview.wss?uid=swg21607001)
Friday, 24 July 2015
Map Drive in DOS
To temporarily map a drive in the Windows command prompt (DOS):
To see which drive letter has been mapped:
To end the temporary mapping:
To map a drive to a specific letter:
To unmap the drive letter:
- pushd \\server\folder
To see which drive letter has been mapped:
- net use
To end the temporary mapping:
- popd
To map a drive to a specific letter:
- net use <letter>: \\server\folder
To unmap the drive letter:
- net use <letter>: /DELETE
Friday, 10 July 2015
SAP Host Agent Notes
SAP Host Agent Troubleshooting:
http://scn.sap.com/docs/DOC-342171862333 - Common Host Agent issues displayed in Agent Administration
http://service.sap.com/sap/support/notes/1862333Host Agent Automatic Upgrade
- Unpack newer agent to /usr/sap/hostctrl/new
- Host agent checks the location every 5 minutes (by default) and upgrades the agent if necessary
Thursday, 18 June 2015
Edit an RFC entry in SM59 which is greyed out
To make changes to an RFC entry which isn't editable follow the steps below:
- Run transaction SM59
- Double-click on the appropriate RFC connection
- Type TOGL into the OK code field
View Solution Manager Diagnostic (SMD) Agent Log files in Solution Manager
- Run transaction SOLMAN_WORKCENTER
- Click on the Root Cause Analysis page tab
- Click on the Host Analysis link
- Filter the system list for the appropriate system
- Click File System Browser
- Navigate to the appropriate folder (typically /usr/sap/DAA/SMDA<nr>/SMDAgent/log) using the folder icons on the left or type in the location manually
View Current Monitoring Status/Alerts in Solution Manager
- Run transaction SOLMAN_WORKCENTER
- Click on the Technical Monitoring page tab
- Click on the System Monitoring link
- Click on the Systems page tab
- Click on the All Systems page tab (and filter for the required SID)
- Highlight the system
- Click System Monitoring -> click Start New Window or Start Embedded
- Select the system
- View the current state of alerts/metrics
Monday, 8 June 2015
Oracle DB Start Up Time
To find the startup time of an Oracle database:
SELECT to_char(startup_time,'DD-MON-YYYY HH24:MI:SS') "DB Startup Time" FROM sys.v_$instance;
Result:
DB Startup Time
--------------------
09-MAY-2015 20:23:13
SELECT to_char(startup_time,'DD-MON-YYYY HH24:MI:SS') "DB Startup Time" FROM sys.v_$instance;
Result:
DB Startup Time
--------------------
09-MAY-2015 20:23:13
Subscribe to:
Posts (Atom)