Error - CLI0111E Numeric value out of range. SQLSTATE=22003 (Linux)
Reason - One of the patch was missing which needs to be installed
Resolution - One of the the rollup Patch was missing, however there are other patches already installed. After the patch (rollup_CC_v2-0_suse-intel_81) installation is completed with a IS Services restart, the job ran successfully.
Tuesday, November 10, 2009
DSDB2 Import (Unable to obtain list of available DB2 Servers)
Reason - This is dsenv set up issue. PATH variable is not correctly defined.
Resolution -
The previous entry for DB2
###############################################################
# DB2 Setup
###############################################################
DB2DIR=/opt/ibm/db2/V9.5; export DB2DIR
DB2INSTANCE=db2clt9; export DB2INSTANCE
INSTHOME=/db2/db2clt9; export INSTHOME
PATH=$PATH:$DB2DIR/bin; export PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$DB2DIR/lib32:$INSTHOME/sqllib/lib; export LD_LIBRARY_PATH
Suggested change:
PATH=$PATH:$DB2DIR/bin:$INSTHOME/sqllib/bin:$INSTHOME/sqllib/adm; export PATH
Save and run dsenv. Restart the services in order to reflect the PATH variable as updated.
Resolution -
The previous entry for DB2
###############################################################
# DB2 Setup
###############################################################
DB2DIR=/opt/ibm/db2/V9.5; export DB2DIR
DB2INSTANCE=db2clt9; export DB2INSTANCE
INSTHOME=/db2/db2clt9; export INSTHOME
PATH=$PATH:$DB2DIR/bin; export PATH
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$DB2DIR/lib32:$INSTHOME/sqllib/lib; export LD_LIBRARY_PATH
Suggested change:
PATH=$PATH:$DB2DIR/bin:$INSTHOME/sqllib/bin:$INSTHOME/sqllib/adm; export PATH
Save and run dsenv. Restart the services in order to reflect the PATH variable as updated.
APT_ORACLE_LOAD_OPTIONS is used to set PARALLEL to FALSE (Tips)
Say the job is running on 8-node configuration File, then
If you set the sqlldr parallel=false and the stage = true, you will get 8 sessions.
If you set the sqlldr parallel=false and the stage = false, you will get 1 session.
If you set the sqlldr parallel=true and the stage = true, you will get 8 sessions.
If you set the sqlldr parallel=true and the stage = true, you will get 1 sessions.
Sqlldr parallel option has to do with how indexes are maintained, not the parallelism of the stage (sqlldr cannot determine the parallelism of datastage).
If you set the sqlldr parallel=false and the stage = true, you will get 8 sessions.
If you set the sqlldr parallel=false and the stage = false, you will get 1 session.
If you set the sqlldr parallel=true and the stage = true, you will get 8 sessions.
If you set the sqlldr parallel=true and the stage = true, you will get 1 sessions.
Sqlldr parallel option has to do with how indexes are maintained, not the parallelism of the stage (sqlldr cannot determine the parallelism of datastage).
XML writer file size limit question (Tips)
Certain o/s have a 2GB file size limit such as the std file system on AIX. See the bottom of this link for info on increasing. http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itame3.doc_5.1/am51_perftune35.htm
If AIX is not your o/s check for similar limits/options.
If AIX is not your o/s check for similar limits/options.
Project Connections lost IS 8.0.1 (Unable to Delete Project)
Error Message - Project Connections lost IS 8.0.1 (Unable to Delete Project)
Reason - The project was in deleting progress when the remote server connections was down. This locked up the project..... The client went in and deleted the file path that the project resided.
Now the Administrator shows a project that doesn't exist. Is there a Universe command that will delete that entry in the project ?
Resolution - Use the command as follows using dsadm@DSHOME/bin/uvsh
DELETE UV.ACCOUNT project_name (to delete a project manually)
If you try next to recreate the original project name and get an error:
DSR.ADMIN: A schema called '...' already exists. This must be dropped before the project can be created.
Then:
LIST UV_SCHEMA (to see if the project schema is listed)
VERIFY.SQL SCHEMA tarp2p FIX
LIST UV_SCHEMA (verify if the project schema is gone - it should be gone)
Other workaround:
The project shows in the DS Administrator because it still exists in the new repository, not DSEngine. If you select the project in DS Admin, you will get an error message and Admin will exit.
There are Scases & Ecases requesting a utility to fix the repository when this occurs, and we are currently investigating productization of an engineering tool to check the repository's integrity.
It is possible to remove the top-level project reference easily from XMETA, by deleting one row from the relevant table, but this leaves all the project objects in the databases. There is also an SQL script that will delete all project objects for any named project, which will clear up the database for you. This is platform-specific so please raise a support case for your current issues.
Reason - The project was in deleting progress when the remote server connections was down. This locked up the project..... The client went in and deleted the file path that the project resided.
Now the Administrator shows a project that doesn't exist. Is there a Universe command that will delete that entry in the project ?
Resolution - Use the command as follows using dsadm@DSHOME/bin/uvsh
DELETE UV.ACCOUNT project_name (to delete a project manually)
If you try next to recreate the original project name and get an error:
DSR.ADMIN: A schema called '...' already exists. This must be dropped before the project can be created.
Then:
LIST UV_SCHEMA (to see if the project schema is listed)
VERIFY.SQL SCHEMA tarp2p FIX
LIST UV_SCHEMA (verify if the project schema is gone - it should be gone)
Other workaround:
The project shows in the DS Administrator because it still exists in the new repository, not DSEngine. If you select the project in DS Admin, you will get an error message and Admin will exit.
There are Scases & Ecases requesting a utility to fix the repository when this occurs, and we are currently investigating productization of an engineering tool to check the repository's integrity.
It is possible to remove the top-level project reference easily from XMETA, by deleting one row from the relevant table, but this leaves all the project objects in the databases. There is also an SQL script that will delete all project objects for any named project, which will clear up the database for you. This is platform-specific so please raise a support case for your current issues.
DS Director Error (Unable to open Specific folder)
Reason - Unable to open a specific folder in the director, it prompts the follwing error message. when I say, 'OK' , Director gets close. But there is no problem with the other folders. The Error message is "Run-time error '457'; This key is already associated with an element of this collection"
Resolution - Perform a rebuild of your Universe indexes
Resolution - Perform a rebuild of your Universe indexes
Cannot open Executable Job file RT_CONFIG319
Error - Cannot open Executable Job file RT_CONFIG319
Re-create the RT_CONFIG96 file as follows:
Resolution: Do the following steps using dsadm account.
From Unix:
a) source the dsenv file ( . ./dsenv)
b) cd to the current project
c) mv RT_CONFIG96 O.RT_CONFIG96
d) $DSHOME/bin/dssh
e) >ED VOC RT_CONFIG5
3 lines long.
----: 2 (Pass this)
0002: RT_CONFIG5
----: R (Pass this)
0002:
----: FILE (Pass this)
"RT_CONFIG5" filed in file "VOC".
f) CREATE.FILE DATA RT_CONFIG96 30
g) Exit and try to compile again.
This problem was reported to engineering and fixed under ecase 78708 - Hashed file headers are getting written into the wrong file and corrupting the hashed files. Since this does not happen frequently, you are better off just correcting the file for now.
Re-create the RT_CONFIG96 file as follows:
Resolution: Do the following steps using dsadm account.
From Unix:
a) source the dsenv file ( . ./dsenv)
b) cd to the current project
c) mv RT_CONFIG96 O.RT_CONFIG96
d) $DSHOME/bin/dssh
e) >ED VOC RT_CONFIG5
3 lines long.
----: 2 (Pass this)
0002: RT_CONFIG5
----: R (Pass this)
0002:
----: FILE (Pass this)
"RT_CONFIG5" filed in file "VOC".
f) CREATE.FILE DATA RT_CONFIG96 30
g) Exit and try to compile again.
This problem was reported to engineering and fixed under ecase 78708 - Hashed file headers are getting written into the wrong file and corrupting the hashed files. Since this does not happen frequently, you are better off just correcting the file for now.
Configuration - IS8.0.1 - Pack SAP 6.0.0
I would recommend using the GUI install on AIX. Here is website on setting up a x-windows client on Windows that I used - http://www.ibm.com/developerworks/aix/library/au-Uwininstall.html
A) Install the SAP Pack on the server - Review the readme file that comes with the SAP Pack installation
SAP RFC Libraries
You Also need the SAP RFC Libraries from SAP Service Market Place. Instructions on getting the SAP Libraries is in the "Install the SAP Pack on the server" section below.
Download SAP RFC Libraries
You get the RFC Libraries from the SAP Service Market Place - https://websmp105.sap-ag.de/swdc (You need a SAP OSS ID to access this site).
Goto : SAP Software Distribution Center -> Download -> Support Packages and Patches -> Entry by Application Group
For AIX we required the 6.40 RFC SDK Kit. The 32 Bit Non-Unicode & 64 Bit Unicode libraries (review the readme file for changes).
Look Under:
SAP NetWeaver
-> Technology components releases prior to SAP NetWeaver
-> SAP WEB AS
-> SAP WEB AS 6.40
-> SAP RFC SDK 6.40
-> AIX 32bit
SAP NetWeaver
-> Technology components releases prior to SAP NetWeaver
-> SAP WEB AS
-> SAP WEB AS 6.40
-> SAP RFC SDK 6.40 UNICODE
-> AIX 64bit
Yes, the SAP Pack Readme file states to use the 32 bit Non-Unicode libraries, and the 64 Bit Unicode libraries. The Readme file also states that for AIX, the 6.4 libraries are required, and not the 7.0 libraries. Refer to the readme file with your SAP Pack for updates.
You will need the RFC Package for both Unicode & Non-Unicode. The SAP Pack Readme mentions which versions are supported on which OS systems. You can review SAP Note 413708 for the 6.40 libraries or 27517 for the 7.0 libraries if the path above doesn't get you to the SAP RFC Files.
You will also need the SAPCAR program from SAP to unpack the RFC files you downloaded.
At the time I wrote this instructions, the SAP RFC SDK AIX 64 Bit was blank on SAP Service Market Place. I had to search for RFC SDK to find it. The files I downloaded were:
AIX 32 Bit SDK RFC_34-20000048.SAR
AIX 64 Bit Unicode SDK RFC_38-20000063.SAR
SAPCAR SAPCAR_4-20000226.EXE
With all 3 files on your system, you can use the command ./SAPCAR_4-20000226.EXE -xvf <*.sar filename> to unpack the .sar files from SAP (you can rename the SAPCAR_4-20000226.EXE file to be sapcar if you wish).
You will need these library files to copy to the server directories. The client will need simular files, but usually gets them by having the SAP Gui installed on the client.
Installing the SAP Pack
Copy the SAP RFC Files to DataStage lib
login as dsadm:
Once complete copy your Lib RFC files to /opt/IBM/InformationServer/Server/DSComponents/lib
For AIX -
Non unicode
librfccm.o
Unicode
libicudata26.so
libicui18n26.so
libicuuc26.so
librfcum.o
libsapu16_mt.so
libsapucum.so
Note: There is an error in the readme file, and the files for Solaris and AIX are reversed.
The files will be in the lib folder where you unpacked the *.sar files downloaded from SAP Service Market Place. You must install both the Non-Unicode & Unicode files, even if you don't plan on using them both. If you get an error writing to /opt/IBM/InformationServer/Server/DSComponents/lib, make sure your logged in as dsadm. Also double check the permissions on the files in the /opt/IBM/InformationServer/Server/DSComponents/lib, I had to do a chmod 755 on the files on my AIX installs.
Start the Install
To start the SAP Pack install, you need to be logged on as root.
Goto the /server/disk1 folder of where you unpacked the SAP Pack Download and execute ./install.bin if doing graphical mode install, or ./install.bin -console if doing console mode.
(or ./install.exe if windows server) from the folder /server/disk1 where you unpaked the file.
As of SAP Pack 5.3.1, there was a bug installing in Console mode (The Pack never asks you for your Suite Admin information). For the time being run the install via the GUI.
====================== INSTALLATION COMPLETE==================
=== POST INSTALLATION STEPS ====
Almost done.. With the Lib Files in place, edit your dsenv file
Prerequisite: A successful installation of WebSphere DataStage Pack on UNIX/Linux
Go to/DSEngine directory Where: = /opt/IBM/InformationServer/Server is the default.
Add following at the end of the file "dsenv":
DSSAPHOME=$DSHOME/..; export DSSAPHOME
Edit the /etc/services file, and add the following entries
General SAP Required Entries
sapdp00 3200/tcp
sapdp01 3201/tcp
sapdp02 3202/tcp
sapdp03 3203/tcp
sapdp04 3204/tcp
sapdp05 3205/tcp
sapdp06 3206/tcp
sapdp07 3207/tcp
sapdp08 3208/tcp
sapdp09 3209/tcp
sapdp10 3210/tcp
sapdp11 3211/tcp
sapdp12 3212/tcp
sapdp13 3213/tcp
sapdp14 3214/tcp
sapdp15 3215/tcp
sapdp16 3216/tcp
sapdp17 3217/tcp
sapdp18 3218/tcp
sapdp19 3219/tcp
sapdp20 3220/tcp
sapdp21 3221/tcp
sapdp22 3222/tcp
sapdp23 3223/tcp
sapdp24 3224/tcp
sapdp25 3225/tcp
sapdp26 3226/tcp
sapdp27 3227/tcp
sapdp28 3228/tcp
sapdp29 3229/tcp
sapdp30 3230/tcp
sapdp31 3231/tcp
sapdp32 3232/tcp
sapdp33 3233/tcp
sapdp34 3234/tcp
sapdp35 3235/tcp
sapdp36 3236/tcp
sapdp37 3237/tcp
sapdp38 3238/tcp
sapdp39 3239/tcp
sapdp40 3240/tcp
sapdp41 3241/tcp
sapdp42 3242/tcp
sapdp43 3243/tcp
sapdp44 3244/tcp
sapdp45 3245/tcp
sapdp46 3246/tcp
sapdp47 3247/tcp
sapdp48 3248/tcp
sapdp49 3249/tcp
sapdp50 3250/tcp
sapdp51 3251/tcp
sapdp52 3252/tcp
sapdp53 3253/tcp
sapdp54 3254/tcp
sapdp55 3255/tcp
sapdp56 3256/tcp
sapdp57 3257/tcp
sapdp58 3258/tcp
sapdp59 3259/tcp
sapdp60 3260/tcp
sapdp61 3261/tcp
sapdp62 3262/tcp
sapdp63 3263/tcp
sapdp64 3264/tcp
sapdp65 3265/tcp
sapdp66 3266/tcp
sapdp67 3267/tcp
sapdp68 3268/tcp
sapdp69 3269/tcp
sapdp70 3270/tcp
sapdp71 3271/tcp
sapdp72 3272/tcp
sapdp73 3273/tcp
sapdp74 3274/tcp
sapdp75 3275/tcp
sapdp76 3276/tcp
sapdp77 3277/tcp
sapdp78 3278/tcp
sapdp79 3279/tcp
sapdp80 3280/tcp
sapdp81 3281/tcp
sapdp82 3282/tcp
sapdp83 3283/tcp
sapdp84 3284/tcp
sapdp85 3285/tcp
sapdp86 3286/tcp
sapdp87 3287/tcp
sapdp88 3288/tcp
sapdp89 3289/tcp
sapdp90 3290/tcp
sapdp91 3291/tcp
sapdp92 3292/tcp
sapdp93 3293/tcp
sapdp94 3294/tcp
sapdp95 3295/tcp
sapdp96 3296/tcp
sapdp97 3297/tcp
sapdp98 3298/tcp
sapdp99 3299/tcp
sapgw00 3300/tcp
sapgw01 3301/tcp
sapgw02 3302/tcp
sapgw03 3303/tcp
sapgw04 3304/tcp
sapgw05 3305/tcp
sapgw06 3306/tcp
sapgw07 3307/tcp
sapgw08 3308/tcp
sapgw09 3309/tcp
sapgw10 3310/tcp
sapgw11 3311/tcp
sapgw12 3312/tcp
sapgw13 3313/tcp
sapgw14 3314/tcp
sapgw15 3315/tcp
sapgw16 3316/tcp
sapgw17 3317/tcp
sapgw18 3318/tcp
sapgw19 3319/tcp
sapgw20 3320/tcp
sapgw21 3321/tcp
sapgw22 3322/tcp
sapgw23 3323/tcp
sapgw24 3324/tcp
sapgw25 3325/tcp
sapgw26 3326/tcp
sapgw27 3327/tcp
sapgw28 3328/tcp
sapgw29 3329/tcp
sapgw30 3330/tcp
sapgw31 3331/tcp
sapgw32 3332/tcp
sapgw33 3333/tcp
sapgw34 3334/tcp
sapgw35 3335/tcp
sapgw36 3336/tcp
sapgw37 3337/tcp
sapgw38 3338/tcp
sapgw39 3339/tcp
sapgw40 3340/tcp
sapgw41 3341/tcp
sapgw42 3342/tcp
sapgw43 3343/tcp
sapgw44 3344/tcp
sapgw45 3345/tcp
sapgw46 3346/tcp
sapgw47 3347/tcp
sapgw48 3348/tcp
sapgw49 3349/tcp
sapgw50 3350/tcp
sapgw51 3351/tcp
sapgw52 3352/tcp
sapgw53 3353/tcp
sapgw54 3354/tcp
sapgw55 3355/tcp
sapgw56 3356/tcp
sapgw57 3357/tcp
sapgw58 3358/tcp
sapgw59 3359/tcp
sapgw60 3360/tcp
sapgw61 3361/tcp
sapgw62 3362/tcp
sapgw63 3363/tcp
sapgw64 3364/tcp
sapgw65 3365/tcp
sapgw66 3366/tcp
sapgw67 3367/tcp
sapgw68 3368/tcp
sapgw69 3369/tcp
sapgw70 3370/tcp
sapgw71 3371/tcp
sapgw72 3372/tcp
sapgw73 3373/tcp
sapgw74 3374/tcp
sapgw75 3375/tcp
sapgw76 3376/tcp
sapgw77 3377/tcp
sapgw78 3378/tcp
sapgw79 3379/tcp
sapgw80 3380/tcp
sapgw81 3381/tcp
sapgw82 3382/tcp
sapgw83 3383/tcp
sapgw84 3384/tcp
sapgw85 3385/tcp
sapgw86 3386/tcp
sapgw87 3387/tcp
sapgw88 3388/tcp
sapgw89 3389/tcp
sapgw90 3390/tcp
sapgw91 3391/tcp
sapgw92 3392/tcp
sapgw93 3393/tcp
sapgw94 3394/tcp
sapgw95 3395/tcp
sapgw96 3396/tcp
sapgw97 3397/tcp
sapgw98 3398/tcp
sapgw99 3399/tcp
For some reason the dir permissions are wrong on the DSSAPConnections folder, so they need to be updated (sap pack readme file tells you to do this). The dstage group needs write permissions.
chmod 775 /opt/IBM/InformationServer/Server/DSSAPConnections
A) Install the SAP Pack on the server - Review the readme file that comes with the SAP Pack installation
SAP RFC Libraries
You Also need the SAP RFC Libraries from SAP Service Market Place. Instructions on getting the SAP Libraries is in the "Install the SAP Pack on the server" section below.
Download SAP RFC Libraries
You get the RFC Libraries from the SAP Service Market Place - https://websmp105.sap-ag.de/swdc (You need a SAP OSS ID to access this site).
Goto : SAP Software Distribution Center -> Download -> Support Packages and Patches -> Entry by Application Group
For AIX we required the 6.40 RFC SDK Kit. The 32 Bit Non-Unicode & 64 Bit Unicode libraries (review the readme file for changes).
Look Under:
SAP NetWeaver
-> Technology components releases prior to SAP NetWeaver
-> SAP WEB AS
-> SAP WEB AS 6.40
-> SAP RFC SDK 6.40
-> AIX 32bit
SAP NetWeaver
-> Technology components releases prior to SAP NetWeaver
-> SAP WEB AS
-> SAP WEB AS 6.40
-> SAP RFC SDK 6.40 UNICODE
-> AIX 64bit
Yes, the SAP Pack Readme file states to use the 32 bit Non-Unicode libraries, and the 64 Bit Unicode libraries. The Readme file also states that for AIX, the 6.4 libraries are required, and not the 7.0 libraries. Refer to the readme file with your SAP Pack for updates.
You will need the RFC Package for both Unicode & Non-Unicode. The SAP Pack Readme mentions which versions are supported on which OS systems. You can review SAP Note 413708 for the 6.40 libraries or 27517 for the 7.0 libraries if the path above doesn't get you to the SAP RFC Files.
You will also need the SAPCAR program from SAP to unpack the RFC files you downloaded.
At the time I wrote this instructions, the SAP RFC SDK AIX 64 Bit was blank on SAP Service Market Place. I had to search for RFC SDK to find it. The files I downloaded were:
AIX 32 Bit SDK RFC_34-20000048.SAR
AIX 64 Bit Unicode SDK RFC_38-20000063.SAR
SAPCAR SAPCAR_4-20000226.EXE
With all 3 files on your system, you can use the command ./SAPCAR_4-20000226.EXE -xvf <*.sar filename> to unpack the .sar files from SAP (you can rename the SAPCAR_4-20000226.EXE file to be sapcar if you wish).
You will need these library files to copy to the server directories. The client will need simular files, but usually gets them by having the SAP Gui installed on the client.
Installing the SAP Pack
Copy the SAP RFC Files to DataStage lib
login as dsadm:
Once complete copy your Lib RFC files to /opt/IBM/InformationServer/Server/DSComponents/lib
For AIX -
Non unicode
librfccm.o
Unicode
libicudata26.so
libicui18n26.so
libicuuc26.so
librfcum.o
libsapu16_mt.so
libsapucum.so
Note: There is an error in the readme file, and the files for Solaris and AIX are reversed.
The files will be in the lib folder where you unpacked the *.sar files downloaded from SAP Service Market Place. You must install both the Non-Unicode & Unicode files, even if you don't plan on using them both. If you get an error writing to /opt/IBM/InformationServer/Server/DSComponents/lib, make sure your logged in as dsadm. Also double check the permissions on the files in the /opt/IBM/InformationServer/Server/DSComponents/lib, I had to do a chmod 755 on the files on my AIX installs.
Start the Install
To start the SAP Pack install, you need to be logged on as root.
Goto the /server/disk1 folder of where you unpacked the SAP Pack Download and execute ./install.bin if doing graphical mode install, or ./install.bin -console if doing console mode.
(or ./install.exe if windows server) from the folder /server/disk1 where you unpaked the file.
As of SAP Pack 5.3.1, there was a bug installing in Console mode (The Pack never asks you for your Suite Admin information). For the time being run the install via the GUI.
====================== INSTALLATION COMPLETE==================
=== POST INSTALLATION STEPS ====
Almost done.. With the Lib Files in place, edit your dsenv file
Prerequisite: A successful installation of WebSphere DataStage Pack on UNIX/Linux
Go to
Add following at the end of the file "dsenv":
DSSAPHOME=$DSHOME/..; export DSSAPHOME
Edit the /etc/services file, and add the following entries
General SAP Required Entries
sapdp00 3200/tcp
sapdp01 3201/tcp
sapdp02 3202/tcp
sapdp03 3203/tcp
sapdp04 3204/tcp
sapdp05 3205/tcp
sapdp06 3206/tcp
sapdp07 3207/tcp
sapdp08 3208/tcp
sapdp09 3209/tcp
sapdp10 3210/tcp
sapdp11 3211/tcp
sapdp12 3212/tcp
sapdp13 3213/tcp
sapdp14 3214/tcp
sapdp15 3215/tcp
sapdp16 3216/tcp
sapdp17 3217/tcp
sapdp18 3218/tcp
sapdp19 3219/tcp
sapdp20 3220/tcp
sapdp21 3221/tcp
sapdp22 3222/tcp
sapdp23 3223/tcp
sapdp24 3224/tcp
sapdp25 3225/tcp
sapdp26 3226/tcp
sapdp27 3227/tcp
sapdp28 3228/tcp
sapdp29 3229/tcp
sapdp30 3230/tcp
sapdp31 3231/tcp
sapdp32 3232/tcp
sapdp33 3233/tcp
sapdp34 3234/tcp
sapdp35 3235/tcp
sapdp36 3236/tcp
sapdp37 3237/tcp
sapdp38 3238/tcp
sapdp39 3239/tcp
sapdp40 3240/tcp
sapdp41 3241/tcp
sapdp42 3242/tcp
sapdp43 3243/tcp
sapdp44 3244/tcp
sapdp45 3245/tcp
sapdp46 3246/tcp
sapdp47 3247/tcp
sapdp48 3248/tcp
sapdp49 3249/tcp
sapdp50 3250/tcp
sapdp51 3251/tcp
sapdp52 3252/tcp
sapdp53 3253/tcp
sapdp54 3254/tcp
sapdp55 3255/tcp
sapdp56 3256/tcp
sapdp57 3257/tcp
sapdp58 3258/tcp
sapdp59 3259/tcp
sapdp60 3260/tcp
sapdp61 3261/tcp
sapdp62 3262/tcp
sapdp63 3263/tcp
sapdp64 3264/tcp
sapdp65 3265/tcp
sapdp66 3266/tcp
sapdp67 3267/tcp
sapdp68 3268/tcp
sapdp69 3269/tcp
sapdp70 3270/tcp
sapdp71 3271/tcp
sapdp72 3272/tcp
sapdp73 3273/tcp
sapdp74 3274/tcp
sapdp75 3275/tcp
sapdp76 3276/tcp
sapdp77 3277/tcp
sapdp78 3278/tcp
sapdp79 3279/tcp
sapdp80 3280/tcp
sapdp81 3281/tcp
sapdp82 3282/tcp
sapdp83 3283/tcp
sapdp84 3284/tcp
sapdp85 3285/tcp
sapdp86 3286/tcp
sapdp87 3287/tcp
sapdp88 3288/tcp
sapdp89 3289/tcp
sapdp90 3290/tcp
sapdp91 3291/tcp
sapdp92 3292/tcp
sapdp93 3293/tcp
sapdp94 3294/tcp
sapdp95 3295/tcp
sapdp96 3296/tcp
sapdp97 3297/tcp
sapdp98 3298/tcp
sapdp99 3299/tcp
sapgw00 3300/tcp
sapgw01 3301/tcp
sapgw02 3302/tcp
sapgw03 3303/tcp
sapgw04 3304/tcp
sapgw05 3305/tcp
sapgw06 3306/tcp
sapgw07 3307/tcp
sapgw08 3308/tcp
sapgw09 3309/tcp
sapgw10 3310/tcp
sapgw11 3311/tcp
sapgw12 3312/tcp
sapgw13 3313/tcp
sapgw14 3314/tcp
sapgw15 3315/tcp
sapgw16 3316/tcp
sapgw17 3317/tcp
sapgw18 3318/tcp
sapgw19 3319/tcp
sapgw20 3320/tcp
sapgw21 3321/tcp
sapgw22 3322/tcp
sapgw23 3323/tcp
sapgw24 3324/tcp
sapgw25 3325/tcp
sapgw26 3326/tcp
sapgw27 3327/tcp
sapgw28 3328/tcp
sapgw29 3329/tcp
sapgw30 3330/tcp
sapgw31 3331/tcp
sapgw32 3332/tcp
sapgw33 3333/tcp
sapgw34 3334/tcp
sapgw35 3335/tcp
sapgw36 3336/tcp
sapgw37 3337/tcp
sapgw38 3338/tcp
sapgw39 3339/tcp
sapgw40 3340/tcp
sapgw41 3341/tcp
sapgw42 3342/tcp
sapgw43 3343/tcp
sapgw44 3344/tcp
sapgw45 3345/tcp
sapgw46 3346/tcp
sapgw47 3347/tcp
sapgw48 3348/tcp
sapgw49 3349/tcp
sapgw50 3350/tcp
sapgw51 3351/tcp
sapgw52 3352/tcp
sapgw53 3353/tcp
sapgw54 3354/tcp
sapgw55 3355/tcp
sapgw56 3356/tcp
sapgw57 3357/tcp
sapgw58 3358/tcp
sapgw59 3359/tcp
sapgw60 3360/tcp
sapgw61 3361/tcp
sapgw62 3362/tcp
sapgw63 3363/tcp
sapgw64 3364/tcp
sapgw65 3365/tcp
sapgw66 3366/tcp
sapgw67 3367/tcp
sapgw68 3368/tcp
sapgw69 3369/tcp
sapgw70 3370/tcp
sapgw71 3371/tcp
sapgw72 3372/tcp
sapgw73 3373/tcp
sapgw74 3374/tcp
sapgw75 3375/tcp
sapgw76 3376/tcp
sapgw77 3377/tcp
sapgw78 3378/tcp
sapgw79 3379/tcp
sapgw80 3380/tcp
sapgw81 3381/tcp
sapgw82 3382/tcp
sapgw83 3383/tcp
sapgw84 3384/tcp
sapgw85 3385/tcp
sapgw86 3386/tcp
sapgw87 3387/tcp
sapgw88 3388/tcp
sapgw89 3389/tcp
sapgw90 3390/tcp
sapgw91 3391/tcp
sapgw92 3392/tcp
sapgw93 3393/tcp
sapgw94 3394/tcp
sapgw95 3395/tcp
sapgw96 3396/tcp
sapgw97 3397/tcp
sapgw98 3398/tcp
sapgw99 3399/tcp
For some reason the dir permissions are wrong on the DSSAPConnections folder, so they need to be updated (sap pack readme file tells you to do this). The dstage group needs write permissions.
chmod 775 /opt/IBM/InformationServer/Server/DSSAPConnections
Friday, November 6, 2009
Oracle PATH search Failure. Could not load "orchoracle".libclntsh.so.10.1
Error - Oracle PATH search Failure. Could not load "orchoracle".libclntsh.so.10.1
Reason - The installation of the Oracle client was not proper because of which it was referred library was missing.
Resolution - The gcc complier was installed with 64 bit initially and on top of that Oracle client was installed. So, it just added the library files relates to 64 bit only. Now, in Datastage dsenv file, the library file it was looking from Oracle was of 32-bit related which was missing. In Oracle installation location we also found tnsnames.ora was missing as well as sqlplus installed with 0 bytes. Proposed for a reinstallation of everything.
Hence, 64 bit gcc compiler was removed and 32-bit compiler installed. Thereafter Oracle client is again done with a fresh installation. So, expected 32 bit library files was received by the Datastage. The issue closed.
Reason - The installation of the Oracle client was not proper because of which it was referred library was missing.
Resolution - The gcc complier was installed with 64 bit initially and on top of that Oracle client was installed. So, it just added the library files relates to 64 bit only. Now, in Datastage dsenv file, the library file it was looking from Oracle was of 32-bit related which was missing. In Oracle installation location we also found tnsnames.ora was missing as well as sqlplus installed with 0 bytes. Proposed for a reinstallation of everything.
Hence, 64 bit gcc compiler was removed and 32-bit compiler installed. Thereafter Oracle client is again done with a fresh installation. So, expected 32 bit library files was received by the Datastage. The issue closed.
AS400 Table lists were not getting populated and system hangs for hours
Error - AS400 Table lists were not getting populated and system hangs for hours.
Reason - AS400 tables expected to be huge and binded with thousand of tables related to N number of schemas. So, while populating it takes hours to get the table extracted from that server. So, if we specify the server and schemas to be used for import in db2cli.ini then the performance would be significantly faster.
Resolution - Add entries like below in the file using db2 userid and password.
%DB2_DIR%/sqllib/cfg/ db2cli.ini
[DUBLIN2]
SchemaList='CRPLIB','MIFDATA20', ...
Incase you want to trace the output of the connection you can add the below 3 lines to check.
[COMMON]
Trace=1
TraceFileName=/tmp/db2clitrace
TraceFlush=1
Reason - AS400 tables expected to be huge and binded with thousand of tables related to N number of schemas. So, while populating it takes hours to get the table extracted from that server. So, if we specify the server and schemas to be used for import in db2cli.ini then the performance would be significantly faster.
Resolution - Add entries like below in the file using db2 userid and password.
%DB2_DIR%/sqllib/cfg/ db2cli.ini
[DUBLIN2]
SchemaList='CRPLIB','MIFDATA20', ...
Incase you want to trace the output of the connection you can add the below 3 lines to check.
[COMMON]
Trace=1
TraceFileName=/tmp/db2clitrace
TraceFlush=1
SQL8002N An attempt to connect to a host failed due to a missing DB2 Connect product or invalid license
Error - SQL8002N An attempt to connect to a host failed due to a missing DB2
Connect product or invalid license. SQLSTATE=42968
Reason - The DB2 license was expired / not applied in the Test Server.
Resolution - Checked the license using the command :
%DB2_DIR%/SQLLIB\BIN>db2licm -l
Which shows the license was not applied on the server side. License applied and hence fixed.
Connect product or invalid license. SQLSTATE=42968
Reason - The DB2 license was expired / not applied in the Test Server.
Resolution - Checked the license using the command :
%DB2_DIR%/SQLLIB\BIN>db2licm -l
Which shows the license was not applied on the server side. License applied and hence fixed.
Subscribe to:
Posts (Atom)
