devidotcom wrote:This issue is yet open.. can anyone help. Now values i used for the environment variables did not work for jobs which had record count >100000.
Please help.
Which environment variables are creating the error? Provide the complete error log.
How do i give u the complete log? Below are the fatal errors.. I agree with you it must be the environment variaibles...
ora_Sample_load,1: Operator terminated abnormally: received signal SIGBUS
main_program: APT_PMsectionLeader(2, node2), player 7 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 8 - Unexpected exit status 1.
devidotcom wrote:ora_Sample_load,1: Operator terminated abnormally: received signal SIGBUS
main_program: APT_PMsectionLeader(2, node2), player 7 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 8 - Unexpected exit status 1.
The "SIGBUS" error is a unix memory access error that occurs when the job tries to point to an invalid memory address or when time-based monitoring is enabled. If you enable row based monitoring, it should fix this problem.
SIGBUS may also occur when the job is attempting to access a value larger than a byte at an unaligned address in the server.
Try to set the APT_MONITOR_INTERVAL=5 (default is 5 - this controls time-based monitoring) and run the job after recompiling it.
Note that if you have the _INTERVAL variable set to anything but 5 (default) it automatically overrides the _SIZE variable setting and reenables time-based monitoring.
I've also seen that SIGBUS error get thrown by buggy Oracle client versions. Mentioned earlier that I thought it would be prudent to see about upgrading your Oracle client.
-craig
"You can never have too many knives" -- Logan Nine Fingers
We have some bitmap indexes on the table, we tried dropping and then ran the job. The job executed perfectly.
We want to use this option now of drop and recreate indexes but the Open/close and Rebuild/Maintenance options are only present when the write method is Load. Any suggestions on how to implement this when the Write Method is Upsert?
Instead of dropping indexes will making the indexes as Unusable is the same as dropping indexdes before the load and then rebuild them once the load is completed. Will this work the same.
