Oracle GoldenGate for SQL Server connection ODBC failed processing method

Oracle GoldenGate for SQL Server is still relatively easy to connect to the Oracle database, as long as the command line is:

ggsci> dblogin Useridalias [alias name]
Or
ggsci> dblogin userid [user name] password [password]

Just fine.

If you are under MS SQL Server, you can also connect via ODBC using the following command:

ggsci> dblgoin sourcedb [DSN]

Here SQL Server and Oracle are different, SQL Server uses the DSN name, and can be connected as well.

But when it comes to extract and replicat, you get the following error:

ERROR OGG-00551 Database operation Failed:couldn ' t connect to DSN001. ODBC error:sqlstate 37000 Native Database error 4060. [Microsoft] [SQL Server Native Client 11.0] [SQL Server] could not open the database requested by login "Baseapp". Logon failure:

The following may be an error in the English system:

ERROR OGG-00551 Database Operation Failed:couldn ' t connect to [dsn001]. ODBC error:sqlstate 37000 Native Database error 4060. [Microsoft] [SQL Server Native Client 11.0] [SQL Server] Cannot open database "db_name" requested by the login. The login failed.

This kind of error hint is very pit, cannot solve this problem by literal meaning, whether modify ODBC inside DSN's login or SQL Server authorization is useless, but actually in Ggsci inside the same operation is no problem.

The way to solve this problem is simple:

Open Microsoft SQL Server Management Studio, under Security, login name, select NT Authority\system->, right-click Properties, Server Role Just tick the sysadmin.

This problem arises because the Goldengate Manager (MGR) service runs as a service, runs under Windows as a system account, and the system account may not have access to the SQL Server database

The other is that we generally install the mixed mode of SQL Server is selected, so the establishment of ODBC connection is the use of integrated account login;

Oracle GoldenGate for SQL Server connection ODBC failed processing method