getting error"Could not load drsdb2.dll" on DB2 UN
Moderators: chulett, rschirm, roy
-
naveenshetty
- Participant
- Posts: 5
- Joined: Wed Feb 07, 2007 3:51 am
- Location: Bangalore
getting error"Could not load drsdb2.dll" on DB2 UN
I'm working on Server jobs with TARGET DB as DB2 UNIX with source as Oracle, and getting error "Could not load drsdb2.dll" , same error i'm getting with DB2OS390 as target, target stage we are using is DRS stage, discussed with environemnts team here, but of no use, please advise me what could be the possible reasons & please provide me any resolution if any,Thanks in advance.
naveen shetty
-
sjfearnside
- Premium Member
- Posts: 278
- Joined: Wed Oct 03, 2007 8:45 am
Although this is an old topic I will post a solution that worked for us instead of starting a new thread.
Our environment is IIS v8.1 on AIX 6.1.
A developer imported a job. They are the owner and belong to a different primary group. The scripts used to execute the job are run as dsadm and group is dstage. Since the job was run under dsadm and the group was dstage the permission granted were other, (5) execute and read.
The job failed with "Could not load drsdbs.dll". The job was deleted from the environment and re-imported with a group of dstage with the correct permissions, (7) execute, write and read.
The job ran successfully.
Hope this will help someone in the future.
Our environment is IIS v8.1 on AIX 6.1.
A developer imported a job. They are the owner and belong to a different primary group. The scripts used to execute the job are run as dsadm and group is dstage. Since the job was run under dsadm and the group was dstage the permission granted were other, (5) execute and read.
The job failed with "Could not load drsdbs.dll". The job was deleted from the environment and re-imported with a group of dstage with the correct permissions, (7) execute, write and read.
The job ran successfully.
Hope this will help someone in the future.
Future Reference...
I had this issue under a reinstall of 8.1 and a new install of 8.5. Both on Windows Server 2003 using the IBM ODBC connection not DataDirect. In both cases uninstalling and reinstalling the DB2 client resolved the issue.
Dave