Intralinkers-
Regarding moving a dataserver and fileserver to a new machine, it is best to
have both machines on the network so you can perform "Move filevault"
commands, which will allow you change references of existing filevaults to a
new fileserver. If you can't see the original fileserver, the DSMU won't
allow you to do the second logon to do the "Move filevault" command. The
link that follows: http://www.ptc.com/cs/tpi/33081.htm is fairly elaborate,
but allows you to get past this via some fancy footwork.

Instead, use SQL commands (here is a good one to store in your bag of
tricks). These are the commands necessary for Oracle to reference a new file
server name and path (back up everything before doing this):

>From a command prompt:
svrmgrl <enter> (that is an ell at the end)
connect internal / internal <enter>
update pdm.pdm_fileserver set fsvhost='your new hostname'; <enter>
update pdm.pdm_pool set poolhost='your new FS hostname',poolpath='new path';
<enter>
exit <enter>

Piece of cake!
Blaine Wright

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

I agree, and have performed this on multiple occasions, however I would
modify by saying...

>From a command prompt:
1)svrmgrl
2)connect  internal/internal
3)select  *  from  pdm.pdm_pool;
4)update  pdm.pdm_pool  set  poolhost  =  '<new_host_name>',  poolpath   =
'<vault_path_#1>'  where  poolid  =  1;
5)commit
6)select  *  from   pdm.pdm_fileserver;
7)update  pdm.pdm_fileserver  set  fsvhost   ='<new_host>';
8)commit
9)exit

I always go back and verify my changes look good by repeating the "select"
command as shown in lines 3 and 6.

Also if you have multiple vault locations you will need to address each
vault location, "new_host_name" stays the same (if all your vaults are on
the same sever) however "poolpath" and "poolid" will be different for each
vault.  Your "poolid" is visibale from the output of step 3. (be sure to
correlate this to the correct filevault).

Also I would recommend you trying this on a test setup, to make sure you are
comfortable with it before you try it on your production system.

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

See intralink Pro/Intralink documentation CD for DSMU. Location of DSMU is
C:\Ptc\Dataserver\Intralink\Bin\Proimge.bat
How to upgrade Dump file after importing it to a new installation of
Intralink in a case new installation is higher version than original:
 
1) create 3 O/S environment variable for Intralink passwords:
 
set  ORA_SYS_PWD=manager
set   PROI_SYS_PWD=dschangeme
set   FS_SYS_PWD=fschangeme
 
You can do it in Dos Shell (in this case they will exist until exiting
shell), or permanently in O/S
 
2) Run the command 
ilink_patches ALL ilnk INTRALINK
Located in 
C:\ptc\Dataserver\Intralink\dbs\ilink_patches\tools\ 
 
You can run 3 separate commands as well
ilink_patches.bat ORACLE ilnk 
ilink_patches.bat SCHEMA English INTRALINK 
ilink_patches.bat VALIDATION English INTRALINK  
 
Note: Change Passwords or command location if you are not using the
defaults

3) In this stage, Intralink references the old vault (as it was when Dump
was file created). Move Vault as follows:

a – copy by O/S explorer the old vault to new location including all Pro/E
files
b – run command svrmgrl.exe located in C:\ptc\Dataserver\Oracle\bin
c - SVRMGR> connect internal/internal
Connected
SVRMGR> select * from pdm.pdm_pool;
1. SVRMGR> update pdm.pdm_pool
2> set poolhost = ‘newhostname’
3>where poolid = 1;
1 row Processed
2. SVRMGR> update pdm.pdm_pool
2> set poolpath = ‘newpath\vaultfoldername’
3> where poolid =1;
1 row processed
3. SVRMGR> update pdm.pdm_fileserver
2> set fsvhost = ‘newhostname’
3> where fsvid = 1;
1 row processed
SVRMGR> commit
Statement processed.
SVRMGR> exit

Note: Don’t miss any character

Good Luck

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

I received some replays; the one that I tried (and worked) was of Bacola
Bob.
Bob wrote
I think these SQL commands are what you need to move things to a new
server
(If the hostname and/or vault paths have changed on the new server):

                                    
                         SVRMGR> connect internal/internal 
                         Connected. 
                         SVRMGR> select * from pdm.pdm_pool; 
                        
        1.       SVRMGR> update pdm.pdm_pool 
                                      2> set poolhost = 'newhostname' 
                                      3> where poolid = 1; 
                        
        2.       SVRMGR> update pdm.pdm_pool 
                                      2> set poolpath ='f:\vaults' 
                                      3> where poolid = 1; 
                         1 row processed. 
                
        3.      SVRMGR> update pdm.pdm_fileserver 
                                    2> set fsvhost= 'newhostname'
                                     3> where fsvid = 1; 
                         1 row processed 
                        
                 SVRMGR> commit 
                         Statement processed. 
                         SVRMGR> exit 


Only Intralink 3.1 is certified for Win2K on the data and file server.

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

Scott,
 
I have used the Oracle ODBC driver in conjunction with ASP scripts to build
a simple web app that queries Intralink for drawings and then views them.
The trick, of course, is figuring out the Intralink schema.  For example, to
find all Adobe PDF files in our Intralink implementation (including
revision, version, mapped files name, etc...) uses this SQL query (yikes!):
 
SELECT PDM_PRODUCTITEM.PINAME, PDM_PRODUCTITEMVERSION.PIVREV,
PDM_PRODUCTITEMVERFILE.PIVFMAPNAME, PDM_PRODUCTITEM.PITYPEID,
PDM_PRODUCTITEMVERSION.RLID, PDM_RELEASELEVEL.RLNAME
FROM PDM.PDM_PRODUCTITEM PDM_PRODUCTITEM, PDM.PDM_PRODUCTITEMVERFILE
PDM_PRODUCTITEMVERFILE, PDM.PDM_PRODUCTITEMVERSION PDM_PRODUCTITEMVERSION,
PDM.PDM_RELEASELEVEL PDM_RELEASELEVEL
WHERE PDM_PRODUCTITEM.PINAME = PDM_PRODUCTITEMVERFILE.PIVFNAME AND
PDM_PRODUCTITEMVERFILE.PIVID = PDM_PRODUCTITEMVERSION.PIVID AND
PDM_PRODUCTITEMVERSION.RLID = PDM_RELEASELEVEL.RLID AND
((PDM_PRODUCTITEM.PITYPEID=141))
 
I used Microsoft Query (Included with Office) to explore Oracle.  If you
paste the SQL from above into MS Query, you will see a graphical depiction
of the schema (obviously a subset).  This seems to work for a simple
application.  I wouldn't want to try and figure out the schema for bills of
material!  Though, if anyone else has done anything similar and figured out
some other useful SQL statements, please share them.
 
Naturally, this approach has its risks since you are bypassing the business
logic of the Intralink application.  I definately would never create
information using this method because of the high risk of data corruption.
 
By the way, Scott, I used to work at one of your competitors, Ethicon
Endo-Surgery! ;)
 
Regards,
 
David

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

Hello,

I recieved more replies asking me to post a summary than actual
explanations, but I did get the information I needed. The Oracle tables must
be manipulated. Be careful when manipulating Oracle tables - PTC will not
help you if something goes wrong. Here is the reply I recieved (thanks to
the individual who replied to me!):

To modify the file cluster name

update pdm.pdm_filespace
set fsname=<NEW FILECLUSTER NAME>
where fsid=<ID OF FILECLUSTER TO RENAME>

To modify the filevault name

update pdm.pdm_pool
set poolname=<NEW FILEVAULT NAME>
where poolid=<ID OF FILEVAULT TO RENAME>

To modify the vault that objects were stored in

(stand alone objects)
update pdm.pdm_productitemverfile
set poolid=<OLD VAULT ID>
where poolid=<NEW VAULT ID>;

(generics)
update pdm.pdm_lovfile
set poolid=<OLD VAULT ID>
where poolid=<NEW VAULT ID>;

Update the OS location of the vaults

update pdm.pdm_pool
set poolpath=<NEW PATH FOR FILE VAULT>
where poolid=<ID OF FILEVAULT TO UPDATE>


Remove unused filevaults  MUST BE EMPTY!!!!

delete from pdm.pdm_filespacepool where poolid=<ID OF FILEVAULT TO 
DELETE>;

delete from pdm.pdm_pool where poolid=<ID OF FILEVAULT TO DELETE>;

Remove unused file clusters  MUST BE EMPTY!!!!!

delete from pdm.pdm_filespace where fsid=<ID OF FILECLUSTER TO DELETE>;


Cheers,
Kerry-Anne Hope

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

Hi all,

Yesterday, we changed the whole folder release scheme through SQL from "a"
to "b" and it seems work, not exactly you case, but I think these maybe the
tables you are looking for.  

pdm.pdm_releaselevel
pdm_pdm_releasescheme
pdm.pdm_folder
pdm.pdm_productitemversion
pdm.pdm_pivrl

regards,

chi-lok YAU
CAD Supervisor
TechTronic Appliances (HK) LTD
24/F CDW Bldg, 388 Castle Peak Rd, Tsuen Wan, HK
Tel:		(852)-24026439
email:	clyau@tti.com.hk

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

--------------------------------------------------------------------
You can not rename folders. Why? Don't know.

If you are very familiar with Oracle manipulations it
can be done there. If you aren't then you can set up
new folders and copy to the new scheme with renamed
files or simply move the files to the new folders.

It is a little tedious and seems old fashioned but it
doesn't take much time and it does work.

If anyone has the files in their workspace that were
checked out prior to the relocation they can simply go
to the Tools pull down menu and synchronize the WS
files with Commonspace. (Sync with CS)

Regards,

Bill
--------------------------------------------------------------------
If you know a bit of programmation and Oracle...

Rename In PDM.PDM_PRODUCTITEMVERFILE  in field PIVFNAME
Rename In PDM.PDM_PRODUCTITEM in field PINAME..

Do a backup just before just in case?

I could maybe... program somethings for you. I already programmed 
somethings
to rename alle the objects we have and merge many object together.

If you have Family Table object.. it could be a bit different.

Good luck...

Marc-Antoine Lemay
Mechanical Designer / ProE administrator /
ProIntralink Admin  / CAD Support / ...
--------------------------------------------------------------------
With 2.0 the 'long way' is it.  I don't know about 3.0.

Jeff Richardson
Sargent Controls & Aerospace
--------------------------------------------------------------------
I would suggest that you have a D.B.A. run a set of SQL commands that
will replace the '_abc' with '_xyz'.  As long as there are no other
objects in other folders(projects) that may contain the '_abc' suffix,
then it should be a simple process.  If I remember correctly, the tables
containing "PINAME" are the only ones that would need to have the
replace command run on them.  As always, make sure that you have a
backup of the database in case of errors, or test it on another server
first.

You could locate all of the objects in CS and attempt to rename them,
but you would be relying on yourself (or others)to correctly enter the
new name.

Good luck and let us know which technique you decide on.

Rob DiMarzio
Pro/E, Intralink Administrator
Quantum Corporation
Boulder, CO 80303
------------------------------
END OF SUMMARY

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

If these words ring a Bell to you !!!
PIVCLASS
PIVFNAME
PIVID
PDM.PDM_PRODUCTITEM
PDM.PDM_PRODUCTITEMVERFILE
PINAME
DEPENDENCYGRAPH
.....
Please send me a E-mail...
I need informations about The INSIDE of Intralink....

Thank's

Marc-Antoine Lemay
malemay@mechtronix.ca

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

What have people experienced when moving large amounts of data in an
Intralink file vault from one server to another?  My vault consists of
33,000 objects that are around 32gb in total size.  I plan on using the DMSU
to move the data but don't know how long the database update will take.  The
actual data move I will do manually and expect it to take a least 3 hours.
I think the database update should be quick since it only has to update the
POOLPATH and POOLHOST in the PDM.PDM_POOL table.  Any experiences would be
greatly appreciated.

Karsten x5074 / Information Systems / East Aurora Building 12B

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


Hey folks,

Got lots of input about copying a database to a test environment.
Summary of inputs is below.


Original posting:
	> Intralink Admins,
	> 
	> We are looking at setting up a test machine to evaluate new
builds of
	> Pro/E and Intralink.  I am looking for a way to copy over the 
	> fileserver
	> AND dataserver from our production machine to the test 
	> machine.  Anyone
	> found a good way to do this?  I know how to duplicate the file
vaults
but I need to duplicate all the metadata with it.
Create dump file from original database.
NEW MACHINE:
Install Intralink - File Server and Data Server Install Intralink Client
and Application Manager Reboot Machine Startup Database and File Server
if not already started.  Try to connect to the Intralink Database. If
Successful - proceed. If not, debug.
Import the dump file into Intralink. This will wipe out what was
installed
and replace
		it with the dump file.
The command is located in:  Drive:\ilink\dataserver\intralink\export
and
the full
		command is: ilink_import manager
Drive:\ilink\dump_files\DUMP_FILENAME.dmp
Put all the files back into the vault location you desire and had setup
during the
		fileserver installation. Usually
Drive:\ilink\vaults\intralink_vault01  .
Now SQL commands must be performed to change the hard coded paths and
server
names
		that are in two tables.
Go to  Drive:\ilink\dataserver\bin
Execute the file called:  svrmgr23
You will get the SVRMGR> prompt. 
Enter:  connect internal/internal  and you should get a response back:
Connected.
If you do not, the database is not started. Enter the command:  startup
to start it up.
Enter:  select * from pdm.pdm_pool ;
Enter:  update pdm.pdm_pool set POOLHOST='new_host_name' ;
Enter:  update pdm.pdm_pool set
POOLPATH='f:\ilink\vaults\intralink_vault01'
;

		If more than one vault - they are identified by a number
in front of
the pool
		name, therefore add the qualifier:   where poolid=#
to the end
of the above
		command before the ;  .
Enter:  select * from pdm.pdm_fileserver ;
Enter:  update pdm.pdm_fileserver set FSVHOST='new_host_name' ;
Enter:  exit    to exit the routine
Hi Jason
There are two things we do:
1.	You need to access Intralink Test server from the same client
without reconfiguring Pro/I client. Then you have to change the way you
access Ilink client.
2.	If you can reconfigure using PTC SETUP every time you change
from Production to Test, then 1st problem is not a issue.  The way I use
it here is.
	1.	Try to have almost an identical platform as your
production server.  ex. I use Solaris same versions for both Prod and
Test.
	2.	I use test server for  restoring just one folder and not
just for testing new releases.
	3.	The way to set up the test server is :
		a)	Install intralink dataserver, fileserver , etc..
		b)	Then export the database from the production
server(This gets you all the metadata information).
		c)	Then Depending on the client,(NT or UNIX), you
need to a import of the dmp file into the test server.
			I think the command is import manager ilink.dmp
where import is the command, manager is the password for system and
ilink.dmp is the dmp file from production server.
		d)	Then  make sure you change all the dataserver
hostnames, fileserver location, database location  on the TEST server.
This you have to do from the server manager using svrmgr command from
the test database bin directory.
		e)	then copy all your filevault files if needed
into your new filevault location(as per the test database)
			Then you have an exact copy of your production
server.
			I hope this answers you question
Good luck
The best way to do this is to follow this procedure:


1.	Export dump file from production Dataserver
2.	Copy Filevaults from production file server to test file server
3.	Import newly created dump file into test dataserver
4.	modify file vaults to point to test file server.
 
	A.	Open Command Window
	B.	Type:  svrmgr32  to enter into servermanager

		C.  Type:   connect internal
	D.	Enter password for user internal:  (default is internal)

		E.  Type:    select * from pdm.pdm_pool;         ENTER 
	(this will display the needed info on the file vaults)
        F.  Type:           update pdm.pdm_pool;                ENTER

        G.    Type:     set poolhost='FILESERVERNAME'        ENTER

        H:     Type:    where poolid=POOLID FOUND IN SELECT COMMAND;
ENTER

        I:    After all vaults are updated Type:      commit; ENTER

        J:     Type:    exit

5.	Restart Dataserver

Look at:
http://www.ptc.com/cs/cs_20/howto/bak1120/bak1120.htm
<http://www.ptc.com/cs/cs_20/howto/bak1120/bak1120.htm> 
Suggested Technique for Backup and Restore of the Database and
Filevaults I used Restore Method 2 to set up my test machine.


very easy, export dump file and copy dump file and all vaults to test
server.
on the test server import the dump file, run ilink_patches, then go into
proimgr and manually move all vaults from "old server" to "new server"
where the old and new server are on the same machine. takes a few times
to get it right, but you must make sure that you are not using the
production server.
Enjoy

Consult the PTC Customer Support web pages to find some insight on this
subject (direct from PTC).  I did a search on Pro/Intralink looking for
items related to the Dataserver.  The TPI to look at is:
http://www.ptc.com/cs/tpi/33081.htm
<http://www.ptc.com/cs/tpi/33081.htm>  Good luck.


There are several ways of accomplishing this...however, the key thing is
factoring all variables that need to be covered.  They are as follows:
(1)	Clients can be pointed to the same FLEXlm license server, or if
a different one is desired on the test server, this needs to be setup on
the server and the client startup command modified to point to it, or
even simpler, a new command created specific to the test case
environment.
(2)	Install from CD on the test Data Server/File Server and either
utilize proimgr to "modify" hostname information, or SQL*PLUS statements
to modify through Oracle (can send you this information if you prefer).
(3)	Copy vaults over to new directory and "modify" location through
proimgr or SQL*PLUS statements.
(4)	Install client software and app manager on test client systems
(if applicable).
(5)	Test out using client, to verify access to test server is
complete.


I'm on NT.  After installing a new dataserver and file server, I just
made a bunch of zip files of the data (I have 7 data vaults), exported
the metadata in the Data Server Management Utility, re-imported and
realigned where the fileserver looked for the vaults in the DSMU (I put
the new vaults on a different drive letter).  Worked pretty easy.  The
zip files copy faster and use less bandwidth than copying 10,000+ files
over the network.  It seems to deal with the file creation process.


Create an export file from production database.
Create a new dataserver from the test database.
Copy the filevaults from the test database to a new location.  Run an
import on the test dataserver.  This will erase your test database, so
be careful.
Index the test dataserver to the new file vaults.
Edit the tnsnames.ora file on the client and point it to the new
datasever.
It's just that simple...
You will need Oracle commands to index the dataserver to the new
filevaults.


have you tried to dump and restore?
the "only" problem you might face is the name of the machines
(fileservers/vaults/dataserver).

Check out PTC TPI33081.
http://www.ptc.com/cs/tpi/33081.htm
<http://www.ptc.com/cs/tpi/33081.htm> 



-----------------------------------
     PANASONIC
Just Slightly Ahead of Our Time
-----------------------------------
C. Jason Schoeneberg
MMCD Mechanical Engineering
770-338-6285

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

Subject: Populating new attribute with old attribute contents in Pro/I

Since Pro/INTRALINK's Pro/ADMIN will not allow you to rename a user-defined
object attribute, the alternative is to create a new attribute and load this
attribute with the value of the old attribute for each object.  According to
PTC's Technical Support, there is no other way to do this but manually.  I've
opened two calls with Tech. Support regarding this and have been told both times
to submit an enhancement request.

I was hoping that the more SQL-savvy/Oracle DBA-type members of this list would
be able to offer a less labor-intensive solution to this problem.  Since I
lacked a database map, I guessed that updating the PDM_PRODUCTITEM_VUDA1 table
would produce the desired results.  I tried the following statement on our test
Pro/INTRALINK Dataserver database:
      UPDATE PDM.PDM_PRODUCTITEM_VUDA1 SET UDA333 = UDA304;
and it appeared to update the table fine but it didn't affect the browser
contents after the COMMIT.

Any help, pointers or direction would be appreciated.  Thanks.

John Macpherson
Engineering & Manufacturing Systems
Carrier Corporation
(315)433-4691
John.Macpherson@Carrier.UTC.com

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

