We have successfully installed and configured DS 8.1 on RHEL 5.0 64 bit version. Initially we had a compiler issue for PX jobs that uses the Transformer stage.
It gave the below error during the compilation of PX jobs that uses the transformer.
<main_program> Error when checking composite operator: Output from subprocess: /bin/ld: skipping incompatible /opt/IBM/InformationServer/Server/PXEngine/lib/liborchi686.so when searching for - lorchi686 /usr/bin/ld: cannot find - lorchi686 collect2: ld returned 1 exit status
Then we configured the compiler and linker settings as given below and that worked.
Is it going to get supported at least in a future release? My problem is basically this. Some of the jobs that does Oracle bulk loads creates .dat files larger than 2 GB. In the current environment I described above, jobs abort the execution as soon as it reaches the 32 bit integer's maximum limit (i.e. dat file size reaches 2147483647 bytes).
That's got nothing to do with 32b v. 64bit, that just a limit configured into your O/S. You need to ensure that you have LFS or 'Large File Support' capabilities and there's no ulimit getting in your way.
-craig
"You can never have too many knives" -- Logan Nine Fingers
[user@machine ~]# cat /etc/sysctl.conf
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.
# Controls IP packet forwarding
net.ipv4.ip_forward = 0
Post your complete, unedited abort message(s) when you hit this limit. And you need to run "ulimit -a" from inside a job (ExecSH) not from the command line to check properly.
-craig
"You can never have too many knives" -- Logan Nine Fingers
TGT_F_ACCOUNT,0: Failure during execution of operator logic.
TGT_F_ACCOUNT,0: Input 0 consumed 7555633 records.
TGT_F_ACCOUNT,0: Fatal Error: Fatal: Error writing to the file: /data/data_mig/pmr/F_ACCOUNT.ctl
node_node2: Player 2 terminated unexpectedly.
main_program: APT_PMsectionLeader(2, node2), player 2 - Unexpected exit status 1.
main_program: Step execution finished with status = FAILED.
Permissions for the .ctl file is given below.
-rw-rw-r-- 1 dsadm dstage 1551 Nov 5 14:21 F_ACCOUNT.ctl
Odd... your 'control file' certainly won't be anywhere near 2GB and that seems to be the file it is having issues with. Have you involved your official support provider yet?
-craig
"You can never have too many knives" -- Logan Nine Fingers
Out of curiousity, what user is the job that failed running under, something other than dsadm? Have you confirmed permissions not just on the file but on the entire path to it?
-craig
"You can never have too many knives" -- Logan Nine Fingers