Pro/Intralink internal error

[jharroun]

We have been getting a couple different Intralink errors when checking out from Commonspace or updating objects in a Workspace.


One error reads:


"Internal error, please refresh the data or restart Pro/Intralink".


The other error reads:


"Pro/INTRALINK has detected an internal error. Please contact Technical Support for assistance. Technical Support will require a detailed description of the actions preceeding this message. Data may also be required. PDMc_QueryCursor_OQL<T>::Initialize"


The proi.log file:


Error Stack:
Error 0:
Message: Pro/INTRALINK has detected an internal error.
Please contact Technical Support for assistance.
Technical Support will require a detailed description of the
actions preceeding this message. Data may also be required.
PDMc_QueryCursor_OQL<T>::Initialize
Arguments:
0: PDMc_QueryCursor_OQL<T>::Initialize
1: /intralink/ilapi/proilbase/inc\cursor.h
2: 390


Error 1:
Message: This error message has internal usage only.
It should be never put into stack.
Please check the online knowledge database at www.ptc.com
and/or contact Technical Support,
Arguments:


Error 2:
Message: This error message has internal usage only.
It should be never put into stack.
Please check the online knowledge database at www.ptc.com
and/or contact Technical Support,
Arguments:


Error 3:
Message: This error message has internal usage only.
It should be never put into stack.
Please check the online knowledge database at www.ptc.com
and/or contact Technical Support,
Arguments:


Error 4:
Message: ToolKit Error : -1652
Arguments:
0: ORA-01652: unable to extend temp segment by 128 in tablespace TEMP


We don't have support anymore, so we can't contact Technical Support like the error suggests.


This error is totally random and in most cases non-repeatable. It happens when you are checking out large assemblies, but not every time. It also happens when checking out small assemblies or just a few parts.


I deleted the .proi directory, created a new workspace and got the same error with the initial check out. So I don't think it is a corrupt local.ddb.


If any of you have seen these errors and may have a potential solution, please let me know. Hopefully I didn't lose anyone with the lengthy post!
Edited by: jharroun

 

[FishNut]

Sounds like your temp tablespace needs resized. (Or could beresult ofillegal immigrants not working Monday)

Look at steps 3 & 4 to check the size. Follow other steps to resize.


1. Start the DSMU by executing the following:
%PROI_HOME%\bin\proimgr.bat for NT
$PROI_HOME/bin/proimgr for UNIX
</PRE>



2. In the DSMU, choose #Server > #Connect Dataserver (NOTE: By default, the Dataserver Password is 'manager').

3. Next, select #Report > #Database Space. If prompted for a value for a threshold, accept the default value of 10 and select #OK.

4. The report will list all tablespaces which are at least 10% full. If not prompted for a threshold, the report will list all the tablespaces. The Tablespace listed in the error message in the .proi.log file may show over 90% full.

5. If the tablespace listed in the error message is the ilnkDATA or ilnkINDEX Tablespace resize the ilnkDATA Tablespace as described in step 6. If any other Tablespace is listed in the error message please contact Technical Support.

6. Choose #Resize > #Tablespace > #IlnkData > #Percent.

7. At this point, the user is then prompted to: 'Enter the percent to increase [Be less than XXX%]'. The percent to increase is up to the discretion of the user. The amount the file size will be increased is a percentage of its current size.

8. The DSMU will give a message: 'RESIZING DATAFILE/S - INCREASE BY XXX%' and ask the user to confirm. Select #OK in the confirmation dialog box to continue with the resize.

9. Once the resize has completed. The message: 'Resize successful' will be given.

10. The datafile has been successfully resized.

 

[jharroun]

Fishnut, thanks for your help. We have been error-free now for three days, so it looks like that was exactly what we needed.

 

[cheMx]

Hi All.





I have this problem, Toolkit=-1 is another way to fix? we have problem