#ATR (20)
Informative Note:
- Created this blog to provide information on SWPM/SUM Errors which I faced when installing SAP Systems on AIX – ORACLE.
- I hope, below error resolutions will help a lot to resolve as quickly as possible if faced during SAP Installation.
Error 1: "No Space left on device"
- Make sure /tmp has atleast 5 GB of free space.
Error 2: "Could not determine DNS Domain of host"
- I have used Short DNS. Make sure whether DNS configured properly. Short FQDN should be added in DNS Server by Network Team. Add entries of FQDN/ShortDNS/IP in hosts file. Error resolved once hosts file entries added from my end.
Error 3: "Error in Selftest during SWPM run"
- https://me.sap.com/notes/0002591258 - 2591258 - ERROR in Selftest. Return code: 3 during start of SWPM Tool (sapinst)
- Case 3: Due to a different hostname by earlier run (using SAPINST_USE_HOSTNAME property) an incorrect host name will be used by the certificate of SAPinst for the HTTPS connection.
- I have run SWPM with Short DNS earlier and then with Full FQDN. Hence, Error popped up. Delete SWPM and Extract again to resolve issue. Use IP to avoid Hostname Config issues.
Error 4: "Soft Resource Limit Stack Size Condition not met"
- Make sure to provide Unlimited Value -- /etc/security/limits file.
- Default -> fsize, stack = -1
Error 5: "XL C/C++ Runtime Prerequisite"
- Install XL C/C++ Runtime accordingly.
Error 6: "Specify the location which contains the correct LABEL.ASC File"
- SWPM will pick all the files by looking into LABELIDX.ASC.
- Once All SAP Software Export files downloaded (Oracle/HANA/etc.,.). Run first Export1.exe application which will extract all 11 export files.
- Once extracted, Place all files with LABELIDX.ASC in Single Folder. Provide LABELIDX.ASC path to SWPM.
- We can also provide each export file LABEL.ASC File if not worked.
Error 7: "Modifying the USER sapadm failed"
- https://me.sap.com/notes/0002360008 - 2360008 - 3004-703 Check "/etc/security/login.cfg" during installation on AIX
- Add /bin/false in login.cfg file inside usw:shells to resolve the issue.
Error 8: "Environment variable DISPLAY is not set"
- For DB2, Oracle -> Simple MobaXterm sufficient instead of other X terminals (Open Text Exceed,etc.,.)
- Use “Adapter” IP for Display.
Error 9: "I/O Completion Ports (IOCP) device status failed"
- “Fix and Check Again” will work sometimes to resolve the error. But make sure to enable I/O Completion ports” manually from our end as well. It will avoid port issues.
- Command: smitty iocp -> Change/Configure both.
- If we didn’t resolve this error, sometimes we will get below “IO Completion port” error while trying to start Listener post installation.
Error 10: "Invalid patch work directory"
- While updating Oracle Patch, we will get above error. Make sure whether oracle base and oracle home env variable set correctly/Run as per SAP Recommendation after setting $IHRDMS, etc.,
- Don’t include 19/ or 19.X.X/ at end of ORACLE_HOME / ORACLE_BASE path.
Error 11: "Missing Write permissions for patch - oradism"
- Provide full authorizations to oradism.
Error 12: " Oracle TNS Listener/Port/FS Errors"
- We would have installed Oracle Database manually before proceeding SWPM SAP Database Instance Installation.
- We should not start Oracle Database once installed manually from our end. It will create unnecessary SID Instance and Listener port will listen to that instance only. This will result in below Errors while trying to continue SWPM for SAP Database Installation.
Listener port already used
Unable to create/edit listener port
No Access for Listener
Cannot mount Database in EXCLUSIVE Mode
Unnecessary collapse on FS permission – Whether Oracle/OraSID should be used - Not Owner.
- I have started Oracle Database by Mistake, and it created new instance.
- SWPM tries to create SID instance with usual SID.WORLD KEY but it’s getting failed since
- Port already used
- Instance already created for SID
- Listener already created for SID Instance.
- To resolve all this, just remove Unnecessary Created Instance(tns)/Listener from X.ORA file.
- Provide oracle:dba authorization to /tmp/.oracle folder and files (sSID.WORLD,sSID,*) since SWPM uses oracle user only.
- In Simple, Use oracle:dba if listener runs with Oracle user. Use oraec3:dba if listener runs with oraec3 user.
- Till SAP Installation, prefer to use oracle user only since SWPM uses Oracle user.
- Once above actions done, SWPM will connect to SID.WORLD KEY without any issues with single instance created for SAP.
Error 13: "Error while attempting to allocate X bytes of Memory"
- In Newly installed OS, 99% --> We will face memory error while running Post-Process Installation of SAP Bundle Patch.
- Run Data Patch Prerequisite separate to find out error trace/logs.
- Command -> $ORACLE_HOME/Opatch/datapatch -prereq
- Error – Latest XML Inventory is not loaded into Table – Occurs at Multiple Scenarios.
- Check Logs to find out root cause. (Memory Error – Mostly occur during SAP Installation)
- To resolve memory issues, just provide full unlimited value for rss, data – SAP Users, Root. Once Script completed, we can also revert it to default values.
- Several Blogs suggests changing DB parameters as a resolution. For above type of scenario (During SAP Installation), Providing Unlimited value sufficient to resolve issue.
- Touch DB parameters (PGA Aggregate Max Limit, Shared Memory,etc.,. ) only if above resolution didn’t work.
Error 14: "TNS – Lost Contact – SQLPLUS Returns 1"
- Above error mostly occurs before creating SAP tablespaces.
- TNS – Lost Contact – SQLPLUS Occurs if port 1521 occupied by another process/previous killed/stopped listener process. Restart VM to clear process.
- Also, occurs if ORACLE_HOME not set correctly. As already mentioned in Error 10, Don’t include / path at end of 19 or 19.X.X. I have changed correctly and restarted VM to resolve the issue.
Error 15: "TNS: no listener"
- TNS – No Listener occurs if SWPM stops Database & Listener for upgrades. Mostly, occur post SAP Tablespaces and SAP DATA Files created.
- Just start TNS Listener with oracle user. As mentioned in Error 13, prefer to use oracle user till SWPM installation completed.
- You can also use oraSID if you don’t face Listener issues.
Error 16: "Cannot mount database in EXCLUSIVE mode"
- SWPM tries to start Database, but I have started manually with Database on Error 15. Stop database and let SWPM start from its end.
Error 17: "Effect of Incorrect SPAM version"
- RARE -> We would have provided wrong SPAM/SAINT file by mistake – Example – For 740 version – Provided 757.
- SPAM/SAINT update will be asked at initial SWPM stage/After SAP SWPM Instance creation/Before SUM execution.
- SWPM won’t show error if wrong version provided. It will proceed without any In-Compatible Package Error since 740 lower package will be available by default (with installation).
- We will face issues (function modules) in Post/Near End of the Installation only which will be very difficult to backtrack and find out SPAM version which we provided is the root cause.
- Below Error popped up when SWPM tries to install additional language post core SAP installation. [Next step – SUM execution]
- Since SAP Instances would have already installed, we can start system and import right SPAM version manually via SPAM transaction.
- Once done, we can restart SWPM and proceed without any issues. I have installed updated one.
Error 18: "Insufficient free space in the database - SPACECHK_OPT"
- We might get Insufficient Space Error for PSAPSR3 tablespace while running SUM.
- We can get extend command in .LST file mentioned in Error pop up.
Error 19: "DBCLONE jobs failure"
- SUM – DBCLONE Jobs failure.
- Make sure to stop other running Jobs. Disable SAP Standard Jobs. Have Free WPs.
- If multiple jobs can’t be triggered due to High CPU/Memory/IO/Performance issues, we can cancel few executing DBCLONE jobs manually and leave others to complete.
- SUM Execution won’t stuck. It will rerun cancelled/failed jobs again once we retriggered. I have cancelled and run as per my convenience.
Error 20: "user_dump_dest parameter deprecated"
- Most of the users try to create control file before upgrades/backup/refresh/post installation.
- We would have tried to view/change user_dump_dest to locate the path which control file will be saved.
- Don’t change user_dump_dest and leave as default.
- We will face above warning while starting database if we change/remove user_dump_dest.
- If we changed by mistake, we can revert using alter command - alter system reset parameter_name scope=spfile/both;
- New Location of Control File -> /oracle/SID/saptrace/diag/rdbms/sid/SID/trace. (Can be seen via Alert_SID log)
WANNA KNOW HOW TO MAKE SYSTEM READY FOR SAP – AIX ORACLE INSTALLATION?
PLEASE REFER BELOW BLOG.
Uninstalling SAP System and Reuse SAP Server for new installation #ATR
Thanks for Visiting!
Please do connect and follow my Linked In Profile.
https://www.linkedin.com/in/ajaytr66/