DB2 Replication Error - Oracle 10g to DB2 8.2 (8.1.8)

[Rafael Faria]

Hello All,

I'm new to DB2, so apologies in advance for any stupid comments I
might make on this replication problem.
Using Information integrator and DB2 8.2 I managed to create a
nickname that references a table sitting on an Oracle 10g Database on
a different server.
I can reference the nickname and retrieve all the information on that
table from my DB2 instance.
The plan now is to have a replica of that table on my DB2 instance. I
decided to set-up a cached table as per DB2 documentation and this
process also created a Materialized Query Table which gets refreshed
using the nickname I had created earlier.
This process also created a replication schedule, capture control
server and control tables, apply control server and control tables on
the source and target databases.
All seemed to be going well but the replication was not working. After
an inspection into IBMSNAP_APPLYTRACE I found the following error
message:

ASN1001E APPLY "DEPARTMENT_MQT_AQ" : "WorkerThread". The Apply
program encountered an SQL error. The ERRCODE is "BF0103". The
SQLSTATE is "08004". The SQLCODE is "-1101". The SQLERRM is
"GCTST01ÿGCTST01". The SQLERRP is "SQLQ003b". The server name is "".
The table name is ""ASN".IBMSNAP_REGISTER".

However I was unable to find a reference that would explain what
ERRCODE BF0103 is and now I haven't got a clue how to fix this
replication problem.

Any help or ideas would be greatly appreciated.

[Joachim Müller]

Rafael,

you can look for the sqlcode. In your case it is 1101:

db2 '? sql1101'
SQL1101N Remote database "<name>" on node "<node-name>" could
not be accessed with the specified authorization id
and password.

Explanation:

A connection to the remote database "<name>" on node
"<node-name>" was requested, and the remote node does not accept
the authorization ID and password combination specified for this
node (either in the remote authorization tables or at runtime).

The request cannot be processed.

User Response:

Resubmit the request with a valid authorization ID and password
combination for the remote system.

sqlcode : -1101

sqlstate : 08004

best regards,
Joachim Müller

"Rafael Faria" <rp******@hotmail.com> schrieb im Newsbeitrag
news:4b**************************@posting.google.c om... Hello All,

I'm new to DB2, so apologies in advance for any stupid comments I
might make on this replication problem.
Using Information integrator and DB2 8.2 I managed to create a
nickname that references a table sitting on an Oracle 10g Database on
a different server.
I can reference the nickname and retrieve all the information on that
table from my DB2 instance.
The plan now is to have a replica of that table on my DB2 instance. I
decided to set-up a cached table as per DB2 documentation and this
process also created a Materialized Query Table which gets refreshed
using the nickname I had created earlier.
This process also created a replication schedule, capture control
server and control tables, apply control server and control tables on
the source and target databases.
All seemed to be going well but the replication was not working. After
an inspection into IBMSNAP_APPLYTRACE I found the following error
message:

ASN1001E APPLY "DEPARTMENT_MQT_AQ" : "WorkerThread". The Apply
program encountered an SQL error. The ERRCODE is "BF0103". The
SQLSTATE is "08004". The SQLCODE is "-1101". The SQLERRM is
"GCTST01ÿGCTST01". The SQLERRP is "SQLQ003b". The server name is "".
The table name is ""ASN".IBMSNAP_REGISTER".

However I was unable to find a reference that would explain what
ERRCODE BF0103 is and now I haven't got a clue how to fix this
replication problem.

Any help or ideas would be greatly appreciated.

[Serge Rielau]

Rafael Faria wrote:

Hello All,

I'm new to DB2, so apologies in advance for any stupid comments I
might make on this replication problem.
Using Information integrator and DB2 8.2 I managed to create a
nickname that references a table sitting on an Oracle 10g Database on
a different server.
I can reference the nickname and retrieve all the information on that
table from my DB2 instance.
The plan now is to have a replica of that table on my DB2 instance. I
decided to set-up a cached table as per DB2 documentation and this
process also created a Materialized Query Table which gets refreshed
using the nickname I had created earlier.
This process also created a replication schedule, capture control
server and control tables, apply control server and control tables on
the source and target databases.
All seemed to be going well but the replication was not working. After
an inspection into IBMSNAP_APPLYTRACE I found the following error
message:

ASN1001E APPLY "DEPARTMENT_MQT_AQ" : "WorkerThread". The Apply
program encountered an SQL error. The ERRCODE is "BF0103". The
SQLSTATE is "08004". The SQLCODE is "-1101". The SQLERRM is
"GCTST01ÿGCTST01". The SQLERRP is "SQLQ003b". The server name is "".
The table name is ""ASN".IBMSNAP_REGISTER".

However I was unable to find a reference that would explain what
ERRCODE BF0103 is and now I haven't got a clue how to fix this
replication problem.

Any help or ideas would be greatly appreciated.

BF must be th3 error code from replication...
SQLCODE 1101 complains about an autthorisation problem trying to access
GCTST01 on node GCTST01.
I leaning far out of the window here, but this is what I would investigate:
You knwo that teh regular II stuff is sane since you can use it.
So it boils down to the fact that this "daemon" uses another id for
which you don't have a user mapping.
Just a guess....

Cheers
Serge

--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab

[Norbert Munkel]

Hello Rafael,

Rafael Faria wrote:

ASN1001E APPLY "DEPARTMENT_MQT_AQ" : "WorkerThread". The Apply
program encountered an SQL error. The ERRCODE is "BF0103". The
SQLSTATE is "08004". The SQLCODE is "-1101". The SQLERRM is
"GCTST01ÿGCTST01". The SQLERRP is "SQLQ003b". The server name is "".
The table name is ""ASN".IBMSNAP_REGISTER".

As others have mentioned before, this seems to be a connection error.
Check the following things:

password-file: defaults to "asnpwd.aut" (this should be somewhere in the
instance-directory).

Database Catalog: Is the capturing database cataloged and reacheable
from the apply-control-servers side?

You can create the password-file with "asnpwd" and check your
configuration with "asnanalyze".

Example:

"asnanalyze -pw $PATH_TO_PASSWORD_FILE/asnpwd.aut -db db1 db2 dbn -la
DETAILED"

would create a file called "asnanalyze.htm" containing a lot of
information about the current status of your replication environment in
the current directory including possible connection probs.

Hope this helps a litle bit.

Regards,

Norbert

[Rafael Faria]

Thanks guys for your help. Where do you look for ERRCODES and SQL
error codes for DB2? We bought the product but we haven't received the
official CD's and doco. Is there a on-line reference? I coulldn't find
it.
I'll investigate further into the authentication problem and let you
know if it worked.
I wasn't aware that you had to specify a password file for the
replication process to use. I thought it would use the same AuthId and
password I specified when I created the user mapping (when defining
the source server definition in my "Federated Database Objects"
folder. If the replication process is not using that mapping to
connect to the source server it will not connect.

Thanks very much for your time and help.

Rafael

Norbert Munkel <[e-mail]> wrote in message news:<aQ**************@se2-cb104-9.zrh1.ch.colt.net>...

Hello Rafael,

Rafael Faria wrote:

ASN1001E APPLY "DEPARTMENT_MQT_AQ" : "WorkerThread". The Apply
program encountered an SQL error. The ERRCODE is "BF0103". The
SQLSTATE is "08004". The SQLCODE is "-1101". The SQLERRM is
"GCTST01ÿGCTST01". The SQLERRP is "SQLQ003b". The server name is "".
The table name is ""ASN".IBMSNAP_REGISTER".

As others have mentioned before, this seems to be a connection error.
Check the following things:

password-file: defaults to "asnpwd.aut" (this should be somewhere in the
instance-directory).

Database Catalog: Is the capturing database cataloged and reacheable
from the apply-control-servers side?

You can create the password-file with "asnpwd" and check your
configuration with "asnanalyze".

Example:

"asnanalyze -pw $PATH_TO_PASSWORD_FILE/asnpwd.aut -db db1 db2 dbn -la
DETAILED"

would create a file called "asnanalyze.htm" containing a lot of
information about the current status of your replication environment in
the current directory including possible connection probs.

Hope this helps a litle bit.

Regards,

Norbert

[Joachim Müller]

Rafael,

welcome to the DB2 Information Center:
http://publib.boulder.ibm.com/infoce...help/index.jsp

that's for Tivoli:
http://publib.boulder.ibm.com/infoce...help/index.jsp

and for pSeries/AIX:
http://publib.boulder.ibm.com/infoce...ries/index.jsp

best regards,
Joachim Müller

"Rafael Faria" <rp******@hotmail.com> schrieb im Newsbeitrag
news:4b**************************@posting.google.c om...

Thanks guys for your help. Where do you look for ERRCODES and SQL
error codes for DB2? We bought the product but we haven't received the
official CD's and doco. Is there a on-line reference? I coulldn't find
it.
I'll investigate further into the authentication problem and let you
know if it worked.
I wasn't aware that you had to specify a password file for the
replication process to use. I thought it would use the same AuthId and
password I specified when I created the user mapping (when defining
the source server definition in my "Federated Database Objects"
folder. If the replication process is not using that mapping to
connect to the source server it will not connect.

Thanks very much for your time and help.

Rafael

Norbert Munkel <[e-mail]> wrote in message
news:<aQ**************@se2-cb104-9.zrh1.ch.colt.net>...

Hello Rafael,

Rafael Faria wrote:

> ASN1001E APPLY "DEPARTMENT_MQT_AQ" : "WorkerThread". The Apply
> program encountered an SQL error. The ERRCODE is "BF0103". The
> SQLSTATE is "08004". The SQLCODE is "-1101". The SQLERRM is
> "GCTST01ÿGCTST01". The SQLERRP is "SQLQ003b". The server name is "".
> The table name is ""ASN".IBMSNAP_REGISTER".
>

As others have mentioned before, this seems to be a connection error.
Check the following things:

password-file: defaults to "asnpwd.aut" (this should be somewhere in the
instance-directory).

Database Catalog: Is the capturing database cataloged and reacheable
from the apply-control-servers side?

You can create the password-file with "asnpwd" and check your
configuration with "asnanalyze".

Example:

"asnanalyze -pw $PATH_TO_PASSWORD_FILE/asnpwd.aut -db db1 db2 dbn -la
DETAILED"

would create a file called "asnanalyze.htm" containing a lot of
information about the current status of your replication environment in
the current directory including possible connection probs.

Hope this helps a litle bit.

Regards,

Norbert