Skip to main content
A
Anonymous
November 1, 2010
Question

Migration error

  • November 1, 2010
  • 6 replies
  • 1643 views

hello,

I am working on migration of Intralink 3.4 to PDM link9.1 M050 with Data Migrator

9.1 M050 .

when I test connection between Source and Targetit returns

com.ptc.migration.util.MigrationException: database link pdmlink_wind_TestDBLinkCreation created in this step could not successfully access the remote database

Anyone does have any idea?

detail error log:

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

---------------------------------------
Main Menu

6 replies

A
Anonymous
November 1, 2010

Although

In addition to that when I when move forward to next steps without testing connection Download Admin Data, Reconcile admin Data, Load Admin Data all option with its sub option works fine(Library folder’s ,user ,Attributes are created on target system as they are on source)

But when I Map Admin Data it gives same error

com.ptc.migration.util.MigrationException: database link pdmlink_wind created in this step cound not successfully access the remote database
Nested exception is: java.sql.SQLException: ORA-12545: Connect failed because target host or object does not exist

Error log as follows:

---------------------------------------------------------------------------------------------------------------------------------------------

---------------------------------------

Main Menu

---------------------------------------

1: Test Connections

2: Download Admin Data

3: Reconcile Admin Data

4: Load Admin Data

5: Map Admin Data

6: Create Document Migration Rules

7: Pre-configuration for Part Creation

8: Cleanup Mapping

9: Exit pre-configuration.

---------------------------------------

>>> Choose an option: 5

User selected:5:Map Admin Data

---------------------------------------

This step will map administrative data between Pro/INTRALINK and target system.

You can perform the following operations.

---------------------------------------

1: Create Migration Site

2: Map USER data

3: Map FOLDER and RELEASE SCHEME/RELEASE LEVEL data

4: Map USER DEFINED ATTRIBUTES data

5: Map FILESERVER data from Pro/INTRALINK

6: Map ALL data (includes Migration Site creation)

7: Go back to the main menu

8: Exit pre-configuration.

---------------------------------------

>>> Choose an option: 1

User selected:1:Create Migration Site

01/11/2010 18:43:36 INFO admin.MigrationSiteLoader - ilDomainId:XXXXXXXXXXXXXXXXXXXXXXXXXXXX

01/11/2010 18:43:49 ERROR util.MigrationException -

com.ptc.migration.util.MigrationException: database link pdmlink_wind created in this step cound not successfully access the remote database

Nested exception is: java.sql.SQLException: ORA-12545: Connect failed because target host or object does not exist

at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:119)

at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:134)

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:254)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:467)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:417)

at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1088)

at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:215)

at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:1038)

at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:1145)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1471)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3888)

at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:4077)

at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:3192)

at com.ptc.migration.admin.MigrationSiteLoader.map(MigrationSiteLoader.java:77)

at com.ptc.migration.admin.MigrationInteractive.performAction(MigrationInteractive.java:440)

at com.ptc.migration.admin.MigrationInteractive.runMenu(MigrationInteractive.java:316)

at com.ptc.migration.admin.MigrationInteractive.performAction(MigrationInteractive.java:351)

at com.ptc.migration.admin.MigrationInteractive.runMenu(MigrationInteractive.java:316)

at com.ptc.migration.admin.MigrationInteractive.run(MigrationInteractive.java:287)

at com.ptc.migration.admin.MigrationInteractive.<init>(MigrationInteractive.java:267)

at com.ptc.migration.admin.MigrationLoadingTest.main(MigrationLoadingTest.java:132)

at com.ptc.migration.admin.MigrationLoadingTest.Main(MigrationLoadingTest.java:163)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.ptc.migration.bin.ILDataloader.execute(ILDataloader.java:136)

at com.ptc.migration.bin.ILDataloader.main(ILDataloader.java:113)

01/11/2010 18:43:49 ERROR bin.ILDataloader - ORA-12545: Connect failed because target host or object does not exist

java.sql.SQLException: ORA-12545: Connect failed because target host or object does not exist

at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:119)

at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:134)

at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:254)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:467)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:417)

at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1088)

at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:215)

at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:1038)

at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:1145)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1471)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3888)

at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:4077)

at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:3192)

at com.ptc.migration.admin.MigrationSiteLoader.map(MigrationSiteLoader.java:77)

at com.ptc.migration.admin.MigrationInteractive.performAction(MigrationInteractive.java:440)

at com.ptc.migration.admin.MigrationInteractive.runMenu(MigrationInteractive.java:316)

at com.ptc.migration.admin.MigrationInteractive.performAction(MigrationInteractive.java:351)

at com.ptc.migration.admin.MigrationInteractive.runMenu(MigrationInteractive.java:316)

at com.ptc.migration.admin.MigrationInteractive.run(MigrationInteractive.java:287)

at com.ptc.migration.admin.MigrationInteractive.<init>(MigrationInteractive.java:267)

at com.ptc.migration.admin.MigrationLoadingTest.main(MigrationLoadingTest.java:132)

at com.ptc.migration.admin.MigrationLoadingTest.Main(MigrationLoadingTest.java:163)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.ptc.migration.bin.ILDataloader.execute(ILDataloader.java:136)

at com.ptc.migration.bin.ILDataloader.main(ILDataloader.java:113)

C:\ptc\ILMigration\bin>

--------------------------------------------------------------------------------------------------------------------------------------------------------

Anyone does have any idea?
Thanks
Shreyas

Anyone does have any idea? Thanks Shreyas
R
rjessen3-Newcomer
3-Newcomer
November 1, 2010
Sounds like you either entered the wrong Intralink server name or port when installing the migration tool.
Otherwise the Intralink server is either not running or has not been locked in migration mode.
S
sdrzewiczewski10-Marble
10-Marble
November 1, 2010
Could also be firewall issues. I saw that a couple of times when rehosting
an Intralink 3.x system to an XP workstation that had been setup with
Windows Firewall.

> Sounds like you either entered the wrong Intralink server name or port
> when installing the migration tool.
> Otherwise the Intralink server is either not running or has not been
> locked in migration mode.
>
B
BobLehman212-Amethyst
12-Amethyst
November 1, 2010
On 11/1/2010 6:43 AM, Stephen Drzewiczewski wrote:
> Could also be firewall issues. I saw that a couple of times when rehosting
> an Intralink 3.x system to an XP workstation that had been setup with
> Windows Firewall.
>

Shreyas
A simple test that you can perform to see if you have database connectivity is to do a sqlplus connection to you ilink and windchill db's

for example

sqplus ilink/inlink@ilink


sqplus wcadmin/wcadmin@wind

If either of these fails you know you have a connectivity issue. If they both pass odds are you have a typo in your setup for the migration run.

--Bob


>> Sounds like you either entered the wrong Intralink server name or port
>> when installing the migration tool.
>> Otherwise the Intralink server is either not running or has not been
>> locked in migration mode.
>>
>> ________________________________
>> From: Shreyas Atre [
C
cadjett1-Visitor
1-Visitor
December 5, 2010
Just ran into this or something similar. Resolution was to add intralink hostname & IP to hosts file (on windchill server).

L Jett
B
BobLehman212-Amethyst
12-Amethyst
December 5, 2010
On 12/4/2010 4:13 PM, Lawrence Jett wrote:
> Just ran into this or something similar. Resolution was to add
> intralink hostname & IP to hosts file (on windchill server).
Lawrence,

That is an interesting observation.  I had something like this and ended
up needing the hostname of the windhill db server defined on the
intralink server. That funky link statement creates a link from the
intralink server to the windhill db server so it can use one
connection.  At least that is what I think it is doing.

If make a habit of always starting with option 1 to test your connection
before running any other migrator command it will point this type of
error out straight away.

One of these days in my infinite spare time I will have to try and break
a migration (I am good at it), but this time break it so by taking out
that hostname definition and see what happens.  I will try to remember
to post back to the group when I do.

--Bob

>
> L Jett
> ----------

Terms & ConditionsCookie settingsAccessibility statement