Sie sind auf Seite 1von 32

Q> 계정 LOCK 풀기(ORACLE)

cmd 들어가서

c:\ 만들어서

저기서 sqlplus "/as sysdba" 하면 oracle 로 들어가진다. (들어가지면 c:\) 가 SQL> 로


바뀐다.)

SQL> alter user <잠긴user 이름> account unlock; //unlock

SQL> alter user <잠긴 user 이름> identified by 비밀번호; // 비번바꾸는 구문

Q> Registry information

Win7 호환성확인 : pdshell

These errors will occur when properties on the file ustation.exe have been set to run in
compatibility mode.

De-selecting compatibility mode resolves the problem.


Q> WIN7 64BIT SERVER/CLIENT WITH PDS2011 CLIENT 연결안될시

Getting error 53 - Then network path was not found.

Answer ID: 16802 | Published 4/16/2012 | Updated 1/7/2014

Relevant Product(s)

BATCH_SERVICES; CloudWorx for PDS; DUAL-P; EERWAY;


FRAMEWORKS_PLUS; PDS_EQUIPIMPORT; PDS_PID; more>>>

Section closed, click or double tap to open

PD_CLASH; PD_DATA; PD_DESIGN; PD_DRAW; PD_EQP; PD_ISO; PD_MDP;


PD_MODEL; PD_ORTHO; PD_PID_DATA_TRANSFER; PD_PROJEC;
PD_REPORT; PD_REVIEW; PD_SHELL; PD_STRESS; PD_SUPPORT; PD_Xpda;
PE_HVAC; PF_MGR; PF_MOD; RD_DINRDB; RD_USRDB; SDNF_IMPORT;
SPLM

Issue

Customer is trying to use PDS 2011 between 2 Windows 7 (64 bits) machines.

One is configured as client and server (SQL Server database and PDS share).

The other is configured as a client. On the client machine, we get the error "53 - The
network path was not found..." when starting PD_Shell.

Environment

N/A

Reported in Version: unknown

Resolution

With Windows 7 as the file and database server, it is necessary to Start the Windows
Remote Registry service on the Windows 7 "server", and set the Startup type to
Automatic. In Windows 7, this service is Stopped and the Startup type is set to
Manual by default.

서버장비: 시스템-제어판-컴퓨터관리-서비스및응용프로그램- REMOTE REGISTRY


시작하면 CLIENT 장비에서 PDS 연결가능.

CLIENT 장비: REMOTE REGISTRY STOP

*Archive Error

network_address value in pdtable_180 blank

Missing information for the unapproved libraries in pdtable_102

* Verify the name and location of the Seed .dgn file for the project

Piping mdlsdz.dgn

Equipment eqpsdz.dgn

Drawing drwsdz.dgn

Raceway rwysdz.dgn

*PDS Express Project Creator

Drive letter to the project not shared

*Registry Entries - See the PDS Setup guide for details on entry locations for 32 or 64
bit.

HKEY_LOCAL_MACHINE on Local Machine


SOFTWARE

Intergraph Common : REG_SZ : C:\win32app\ingr\share

HKEY_ LOCAL_MACHINE on Local Machine

SOFTWARE

Microsoft

Command Processor DisableUNCCheck : REG_DWORD : 0x1

HKEY_ LOCAL_MACHINE on Local Machine

SYSTEM

This error can be caused by a firewall. In this case the Symantec Endpoint Protection
firewall caused the error. Symatec Enpoint Protection has a firewall configuration
policy that was set by their IT group. Once they removed that policy, the error
stopped.

Q> While working in Equipment Modeling the fatal error "Error retrieving
ILK" Appears.

Answer ID: 16171 | Published 12/9/2011 | Updated 12/12/2013

Relevant Product(s)

BATCH_SERVICES; CloudWorx for PDS; DUAL-P; EERWAY;


FRAMEWORKS_PLUS; PDS_EQUIPIMPORT; PDS_PID; more>>> Section closed,
click or double tap to open
Issue

Error: While working in Equipment Modeling the fatal error "Error retrieving ILK"
appears.

Environment

Reported in Version:

Resolution

Add Registry keyin per Microsoft:

On the server, Run the following string from the Command Prompt Window:

reg add
"HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters" /v
DisableLeasing /t REG_DWORD /d 1 /f

https://smartsupport.intergraph.com/app/answers/detail/a_id/16171/kw/ilk

Q> ORACLE RAM CPU SPEED

Normally, CPU is not nearly as important as I/O for database. Make sure you have a
very fast disk system and enough RAM to cache most or all of the database (which
lightens the hit on the disk for reads).

Or in other words, it won't matter if you buy the fastest CPU on earth if you don't
have fast storage.
Q>

Pdtable_103 PDS Version

4 5.4

5 6.0 to 6.1

6 6.3 to 6.4

7 7.0 to 7.1

8 7.2

9 7.3, 8.0, 8.0.1

10 9.0 to 10.0

11 11.0 to 12.0

Q> Import Project Retrieval fails. Error: Option Not Valid for Archived Version No.

Product version number is missing or 0 in lst_file.cpio

Add the correct version number to the file will resolved the problem

1. Rename lst_file.cpio to lst_file.cpio.zip and unzip it

2. Open lst_file.cpio a text editor and add correct PDS Version Numbering to the
second line.

3. Zip it and rename it back to the original file's name.


Example:

PDS12

11

import.cpio

project.ddl project.ddl myserver f:\PDS12\project\

design.ddl design.ddl myserver f:\PDS12\project\

reference.ddl reference.ddl myserver f:\PDS12\project\

eqp.ddl eqp.ddl myserver f:\PDS12\project\

Q> Cannot Drop Schema

Error trying to drop schema. Schema password does not match existing password for
this user

Resetting the schema password to NO password:

RIS Schema Manager -> Schema Definition -> Modify Schema Password

For PDS do not put a password on the schema. Only the database username and OS
username should have passwords.

Q> Change RIS Schema Password Without Knowing Current Schema Password

Go into SQL*Plus as the database user who owns the schema


connect schemadbusername/password@NetServiceAlias

select * from ri05_t01;

Verify that the schema_password has an encrypted password.

The following command will remove the schema password.

update ri05_t01 set schema_password='*';

Perform the select above to verify that the schema_password=*

commit;

The user must get out of RIS Schema Manager and log back in so that the schema will
be read again in RIS. The password should be removed

Q> ORACLE EXPIRED 만료기한연장

< 명령어참고>

SELECT RESOURCE_NAME, LIMIT FROM DBA_PROFILES WHERE


PROFILE='DEFAULT';

ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME


UNLIMITED;
SQL> SELECT USERNAME, ACCOUNT_STATUS, LOCK_DATE,
EXPIRY_DATE

2 FROM DBA_USERS

3 WHERE USERNAME = 'GHOST'

4 ORDER BY CREATED;

SQL>

SELECT USERNAME, ACCOUNT_STATUS, LOCK_DATE, EXPIRY_DATE


FROM DBA_USERS WHERE USERNAME = 'GHOST'

oRDER BY CREATED;

SELECT USERNAME, ACCOUNT_STATUS, LOCK_DATE, EXPIRY_DATE

FROM DBA_USERS

WHERE USERNAME = 'GHOST'

ORDER BY CREATED;

SELECT USERNAME, ACCOUNT_STATUS, LOCK_DATE, EXPIRY_DATE


FROM DBA_USERS;

<< 해결>>

SQL> conn dd_y2pw/dd_y2pw

...the password has expired...

Changing password for dd_y2pw

New password :

Retype new password :

....

<< 해결>>

SQL> conn dd_y2pw/dd_y2pw


...the password has expired...Changing password for dd_y2pwNew password :Retype
new password :

이오류는오라클11g 에서는기본적으로120 일마다패스워드를바꿔야한다는정책으로말미암아

3 개월지나면기존의패스워드로는접속이안되게되는것을뜻합니다.

10g 까지는이디폴트셋팅이UNLIMITED 였으나11G 에서는이것이120 일이디폴트입니다.

>>> 패스워드기본값확인쿼리

SQL> SELECT RESOURCE_NAME, LIMIT FROM DBA_PROFILES WHERE


PROFILE='DEFAULT';

RESOURCE_NAME LIMIT

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

COMPOSITE_LIMIT UNLIMITED

SESSIONS_PER_USER UNLIMITED

CPU_PER_SESSION UNLIMITED

CPU_PER_CALL UNLIMITED

LOGICAL_READS_PER_SESSION UNLIMITED

LOGICAL_READS_PER_CALL UNLIMITED

IDLE_TIME UNLIMITED

CONNECT_TIME UNLIMITED

PRIVATE_SGA UNLIMITED

FAILED_LOGIN_ATTEMPTS 10

PASSWORD_LIFE_TIME UNLIMITED

RESOURCE_NAME LIMIT

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

PASSWORD_REUSE_TIME UNLIMITED

PASSWORD_REUSE_MAX UNLIMITED
PASSWORD_VERIFY_FUNCTION NULL

PASSWORD_LOCK_TIME 1

PASSWORD_GRACE_TIME 7

즉그러니.. 이것을다시UNLIMITED 로바꾸는작업이필요합니다.

ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;

물론관리자로접속하셔야합니다.

헌데이퀴리를날려도해당유저의EXPIRY_DATE 는그대로입니다.

>>> 사용자패스워드확인퀴리

SQL> SELECT USERNAME, ACCOUNT_STATUS, LOCK_DATE,


EXPIRY_DATE

2 FROM DBA_USERS

3 WHERE USERNAME = 'GHOST'

4 ORDER BY CREATED;

USERNAME ACCOUNT_STATUS LOCK_DAT EXPIRY_D

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

GHOST EXPIRED 11/04/10

이럴때는해당유저로다시접속해서패스워드를새로넣어주시면됩니다.

SQL> conn ghost

비밀번호입력:

ERROR:

ORA-28001: the password has expired

ghost 에대한비밀번호를변경합니다.

새비밀번호:

새비밀번호다시입력:
비밀번호가변경되었습니다.

연결되었습니다.

SQL>

다시확인해보죠.

SQL> conn system/XXXXX

연결되었습니다.

SQL>

SQL> SELECT USERNAME, ACCOUNT_STATUS, LOCK_DATE,


EXPIRY_DATE

2 FROM DBA_USERS

3 WHERE USERNAME = 'GHOST'

4 ORDER BY CREATED;

USERNAME ACCOUNT_STATUS LOCK_DAT EXPIRY_D

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

GHOST OPEN

이제정상으로돌아왔네요. ^^

Q> 암호기한없애기(위내용)

SELECT RESOURCE_NAME, LIMIT FROM DBA_PROFILES WHERE


PROFILE='DEFAULT';

ALTER PROFILE DEFAULT LIMIT PASSWORD_LIFE_TIME UNLIMITED;

Q> 암호대소문자구분무시
alter system set sec_case_sensitive_logon=false;

Q> listenr.ora 설정

# listener.ora Network Configuration File:


D:\app\Administrator\product\12.1.0\dbhome_1\network\admin\listener.ora

# Generated by Oracle configuration tools.

SID_LIST_LISTENER =

(SID_LIST =

(SID_DESC =

(SID_NAME = CLRExtProc)

(ORACLE_HOME = D:\app\Administrator\product\12.1.0\dbhome_1)

(PROGRAM = extproc)

(ENVS =
"EXTPROC_DLLS=ONLY:D:\app\Administrator\product\12.1.0\dbhome_1\bin\orac
lr12.dll")

LISTENER =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = 장비명 )(PORT = 1521))

(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))


)

Q>

*********************************************************************
**********

* RIS Error: RIS_E_NO_SCHFILE_LOCATION (0x8a949a1a) *

**

* default schema pd_UHP *

**

* The location of the RIS schema file has not been determined. You may *

* need to execute a locate schema file command. *

*********************************************************************
**********

SCHEMAS 를 다시 생성한다.!

Q> 자격 증명 관리

네트워크 연결 암호 자동 설정

Q> ORACLE SQL DEVELOPER

시스템 환경변수 PATH 추가


C:\Program Files\sqldeveloper\jdk\jre\bin\server ;C:\Program
Files\sqldeveloper\jdk\jre\bin

Q> Write Permission Denied

Users cannot open models in new PDS project. The error is Write Permission Denied

*path_name and network_address values in pdtable_113 does not match actual file
location

Relocate the file to match the PD_schema

Update values in pdtable_113

Example using RIS Interactive: update pdtable_113 set path_name =


'e:\proj1\models\piping\dgn\' where model_index_no=x

*Write permission denied error was due to inadequate permissions to the project

*Verify the drive letter where the project is located is not shared as
driveletter$ (example D$). This is reserved for administators. Drives with PDS project
cannot have a $ share

Q> ORA-12170 Connection Timed Out

Make sure the Windows Firewall is turned off or open the port assigned for SQL Net
(1521 by default).

Q> Delayed Write Failed Error


*Disable opportunistic locking

Open Regedit and go to:

HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters and look for


EnableOplocks

If missing create it as a new DWORD value. Set it to 0.

*Modify System Configuration:

Run Add/Remove Windows Programs from the control panel:

Select Add/Remove Windows Components --> Uncheck "Update Root Certificates"


--> Next --> OK.

*Disable Write Caching on the hard drive on the server.

*Error message when you write a file to a server from a Windows XP-based or a
Windows 2000-based computer: "" Delayed Write Failed

See Microsoft Links:

http://support.microsoft.com/kb/321733

http://technet.microsoft.com/en-us/library/bb490821.aspx

Q> MSSQL Error -10004, Underlying DBMS Could Not Open Database

RISMSFDS 5.6

Reported in Version: RISMSFDS 5.6

MSSQL 2005
Log in to the DB server and make sure user can connect to the DB using SQL Server
Management Studio. Make sure this login has DBO permission for the PDS database.
Verify that the usernames are displayed under Databases > PDS > Security > Users.

Make sure that the installation of SQL Server uses the Default Instance for RIS/PDS.
If there is already a default instance (one identified by the name of the computer on
which you are install SQL Server), RIS won't be able to communicate with the SQL
Server. You can have only one default instance per computer (any other instances will
be called a named instance).

Also, you need to use this script when creating users:

CREATE LOGIN pd_proj1 WITH PASSWORD = 'pd_proj1', CHECK_POLICY =


OFF

go

USE PDS

go

CREATE USER pd_proj1 FOR LOGIN pd_proj1

go

Create Schema pd_proj1 authorization pd_proj1

go

Alter user pd_proj1 with default_schema = pd_proj1

go

sp_addrolemember 'db_owner', 'pd_proj1'

go

Q>Failed to Open Label Description Library

Run Grantall utility: Grantall Utility


Q> PDS and Citrix Troubleshooting

*System Fault 5, MDL abort in DITEMS, Unable to start Ditems.ma

System Fault 5, MDL Abort in DITEMS

*No printer in the list when trying to plot clash on Citrix box

With Citrix batch queue must be piped to a non Citrix machine

PDS will list the printers on the piped machine

No printers created on piped machine

*The variables, MS_USERPREF, MS_FONTRSC, and MS_CONFIG, are hard coded


in PDS to point to the specific files

MS_UMENUPREF=c:\win32app\ingr\pdshell\menu\umenupref.rsc

MS_FONTRSC=c:\win32app\ingr\pdshell\font\pdsfont.rsc

MS_CONFIG=c:\Bentley\Program\MicroStation\config\msconfig.cfg

*The new variables were created to provide the capability to use different values
(hence, point to different files) for hard coded variables.

?PDS_USER_UMENUPREF variable is used for MS_USERPREF

?PDS_USER_FONTRSC variable is used for MS_FONTRSC

?PDS_USER_CONFIG variable is used for MS_CONFIG

*Here is an example pds.cmd file:

@rem = '

@echo off
pdsperl %0.cmd %1 %2 %3 %4 %5 %6 %7 %8 %9

goto endofperl

';

$ENV{'GRAPHICS_TOP'} = 'YES';

$ENV{'PROJ_FILE'} = 'c:\pds\\';

$ENV{'PROJ_ADDR'} = 'brewster7';

$ENV{'PDS_USER_UMENUPREF'}='c:\win32app\\ingr\\pdshell\\menu\\newpre
f.rsc';

$ENV{'PDS_USER_FONTRSC'}='c:\win32app\\ingr\\pdshell\\font\\webfont.rsc'
;

$ENV{'PDS_USER_CONFIG'}='c:\bentley\\program\\microstation\\config\\gbco
nfig.cfg';

$PD_SHELL = $ARGV[0];

$appname = "$PD_SHELL\\bin\\pdshell";

# If more than one argument, then

# first argument is the path to the utility

# second argument is the executable file name

if($#ARGV>$[)

$appname=$ARGV[0].$ARGV[1];

if($#ARGV>$[+1)

shift;

shift;
foreach $argi (@ARGV)

$appname .= ' '.$argi;

system "$appname";

__END__

Q> MicroStation User Configuration Files

MicroStation User Configuration Files .ucf

PDS by design has hard coded the USTN_USERNAME variable to use the
untitled.ucf file.

Note: PDS 11 and above does allow for individual msconfig.cfg files using the
PDS_USER_CONFIG variable setting in pds.cmd

Q> Oracle Does Not Install When Hostname Includes Underscore

Beginning with Windows 10 and Oracle 12.1.0.2, Microsoft and Oracle will enforce
the Internet Host Table Specification RFC 952 which mandates that component
hostname labels can contain only alphanumeric characters. Hostnames using
underscores ('_') are not allowed.

Refer to Oracle Support Articles 1603775.1 and 1957895.1 and Microsoft KB


101785.
Q> Grant All Is Failing

Recommend that user create his own grant all, below are the steps:

1. Start RIS Interactive and select the schema

2. Key in the following sql statement

select 'grant all on', table_name, 'to public;' from ris5tables where table_type='T'

3. Execute and select Options > Fetch All Rows

4. Select Save Results and specify an output file such as grant1.sql

5. Edit the output file and delete the two heading lines at the top of the file. Insert a
line to identify the default schema from step 1

default schema pd_proj1;

6. Start risbatch (Start -> All Programs -> RIS06.00 -> RIS Batch) and key in

read \path\grant1.sql

constant table_name constant

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

grant all on pdtable_101 to public;

grant all on pdtable_102 to public;

grant all on pdtable_103 to public;

grant all on pdtable_104 to public;

grant all on pdtable_105 to public;

grant all on pdtable_111 to public;

grant all on pdtable_112 to public;


Q> Load Weld Numbers and Delete Weld Numbers buttons are disabled

The two buttons are enabled only when weld numbering type is set to User Defined
Weld Numbers in Revise Weld Numbering Settings

To enable the buttons, click on

Revise Weld Numbering Settings > Toggle Weld Numbering Type and set to User
Defined Weld Numbers > Accept

Q> Retain Existing Weld Number on Pipeline

1. Select Pipe Design Data Manager>Weld Numbering>Revise Weld Number Setting

2. Under Remodel Revision Control toggled to Reassign from intact half

Q> Hyphen in the place_rdb_specialty Command

Hyphen in Tag number of Piping Specialty is not accepted in piping assembly:

PLACE RDB_SPECIALTY ,32-01A, BY CP2

Program does not take hyphen in the place_rdb_specialty command

Define a variable and assign the tag number to it

Then call the place_rdb_specialty command


See below sample:

TAG_NO = '32-01A'

PLACE_RDB_SPECIALTY, TAG_NO, BY CP2

Q> Pipe Disappears If It Is Approved

Levels 41, 42, and 43 tuned off

Approving pipe moves graphics to different level

Q> Error Selecting Piping Discipline

The symbology in the project was set to Fluid Code and the pipecat2.txt was missing
from the project directory. To resolve the error: retrieve the file from the project
backup. It can also be copied from C:\win32app\ingr\PDSHELL\categ\ folder if it is
the same as the delivered one.

Missing pipecats2.txt in the project directory.

Q> Model Seedfile Contains Category Control Levels Set to Zero

Project Administrator > Project Data Manager > Seed > Revise (on the Piping Model
Data) and then returns to the Project Data Manager screen, error: Model Seedfile
Contains Category Control Levels Set To Zero

-> One of the levels in the seed file is set to zero

Project Administrator - Project Data - Seed - Revise Piping Model - Level and Color.
If any of the levels are zero, change to non-zero value

Q > Maximum Size of Models


By default, in the Seed Data, the max size is set to 2500 blocks (about 1.2 MB)

Change the Seed Data of the model and increase it Model Size Exceeded

Note : Increasing the Model Size will effect the load time of the model

Q> Increasing the Oracle Processes Parameter

Logon to the database using SQL Plus and run:

alter system set processes=300 scope=SPFILE;

oracle 서버에 동시에 접속할 수 있는 사용자의 해당os process 의 최대 갯수

Shut down the database and then restart the database. If there are users connected, use
a shutdown normal to avoid forcing the users out of Oracle.

Q> Determining Oracle Version

Connect to SQL*Plus

$ sqlplus /nolog

SQL> conn / as sysdba

SQL> select * from v$version;

Or log into SQL*Plus specificing an Oracle user.

Q> How can I determine my PDS database tablespace names using SQL Plus?

Enter this at the SQL> prompt: Select name from v$tablespace;


Q> Auto Extend a Tablespace

Technically, a tablespace cannot be placed in autoextend. Datafiles are put to an


autoextend state.

To use Enterprise Manager/DB Control, go through the GUI to identify the datafile
and modify it to autoextend.

If you are using the command line, first identify the datafile(s) for the tablespace in
question. Where the name USERS is in the SQL statement below, use your tablespace
name in all CAPS.

SQL> select file_name from dba_data_files where tablespace_name = 'USERS';

FILE_NAME

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

D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF

Then issue the following (note that the full path is in single quotes and must be used).

SQL> ALTER DATABASE DATAFILE


'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\USERS01.DBF'
AUTOEXTEND ON NEXT 1024K MAXSIZE UNLIMITED;

Database altered.

In this example the next increase is set to 1 mb and will allow unlimited file size. The
next increase size value can be set to be larger based on your need.

Q> Oracle Services Stop During the Night


There is a recurring issue of a 64 bit Oracle database being shut down during the
evening. If the Oracle Service and Listener Service are restarted, everything runs okay
for a while.

The alert log shows a write error to a database file causing the database to shutdown.
That is usually an indication that a system backup is holding the file when Oracle is
trying to write to it. Check to see if the directories are included in the backup list. If so,
either exclude them or ensure that the database is shutdown while the backup is in
progress.

System backup is locking a database file.

Q> How do you calculate the number of Oracle processes setting for PDS?

PDS users can take 5 to 8 process per user, so for10 users, up to 80 could be used. For
50 users, up to 480 process.

Q> Logging Into SqlPlus as SYSDBA

At a command prompt type:

sqlplus /nolog

SQL>connect username/password@alias as sysdba

Q> Enterprise Manager Console is Unable to Start After Domain Change

10g R2 Database Control (Enterprise Manager Console) is unable to start after


domain change

-> Recreate the Database Control (Enterprise Manager Console)


1.Connect to SQLPLUS as a DBA ?DROP USER SYSMAN CASCADE;

*DROP ROLE MGMT_USER;

*DROP USER MGMT_VIEW CASCADE;

*DROP PUBLIC SYNONYM MGMT_TARGET_BLACKOUTS;

*DROP PUBLIC SYNONYM SETEMVIEWUSERCONTEXT;

2.Open a command prompt on the Oracle database server and run the following
statement to remove the existing configuration files:

CMD> EMCA -deconfig dbcontrol db -repos drop

3.In the same command prompt, re-create the DB Console repository by executing the
following:

CMD> EMCA -config dbcontrol db -repos create

Need to reconfigure Database Control (Enterprise Manager Console) after a domain


change.

Q> Manually Stopping and Startting DB Control

1.Open a command prompt.

2.To stop dbconsole:

CMD>emctl stop dbconsole

3.To start dbconsole:

CMD>emctl start dbconsole


Q> Cannot find spec and table implied item in table 34 of the mto schema.

Spec and table implied items are populated into table 140, not table 34.

Q> Mapping fluid code (codelist) to description in the MTO schema.

Map pdtable_12.fluid_code to pdtable_250.std_note_code where


pdtable_250.std_note_no = 125.

Eample Query:

SELECT pdtable_12.line_id, pdtable_250.long_descr

FROM blapdb.mto_train.pdtable_12 pdtable_12, blapdb.mto_train.pdtable_250


pdtable_250

WHERE pdtable_12.fluid_code = pdtable_250.std_note_code AND


((pdtable_250.std_note_no=125))

Q> Quantity of Bolts Extracted From Mto Schema Does Not Match Iso Drawing

Re-run Material Data Publisher with selecting Iso Mating Data Behavior option.
Selecting Forced Publishing of Models in the first re-run to get new data.

Pd_iso and Material Data Publisher work differently in assigning the ownership of
implied materials (bolts, gasket and weld). New option was added in version 9.00: Iso
Mating Data Behavior which tells program to assign the ownership of implied
material in the same way as pd_iso does.

Q> Create Schema - Command Line

Here is a command line to create a schema for Oracle using RISORADS.


create schema sch1 on database ( oracle, dbname orcl , dir
D:\oracle\product\10.2.0\db_1 , remote ( tcp DB_servername ) , ostype nt , osuser
OS_username.OS_password ) user Oracle_username.Oracle_password;

Here is a command line to create a schema for MSSQL using RISMSFDS:

create schema sch1 on database ( mssql, dbname risdb1 , remote ( tcp


DB_servername) , ostype nt , osuser OS_username.OS_password) user
DB_username.DB_password;

You can create a batch file with the create schema command in it and then run the
command from risbatch using the following syntax:

risbatch -i input.sql -o output.txt

Q> Desktop Heap Summary

Errors occur when a large number of RIS/PDS connection have been made to the
server.

*Application Error: The application failed to initialize properly (0xc0000142)

*RIS Error: RIS_E_READ_ERROR (0x8a949f3a)

*RIS_E_SERVER_NETWORK_ERROR (0x81949f3a)

*RIS Error: NET_E_READ_ERROR (0x89cd81da)

*RIS_E_INV_OPEN_DB (0x8a948e22)

*Oracle Error -21561 - ORA-21561: OID generation failed

*May also see a 'KERNAL32.DLL' or 'USER32.DLL' error occur

*ORA-12640: Authentication adapter initialization failed

*ORA-00022: invalid session ID; access denied


*Turning Autocommite On/Off for PDS

-> To correct this problem, increase the size of the desktop heap:

1.Run Registry Editor (Regedt32.exe).

2.From the HKEY_LOCAL_MACHINE subtree, go to the following key:


\System\CurrentControlSet\Control\Session Manager\SubSystems

3.Select the Windows value.

4.From the Edit menu, choose String.

5.Increase the SharedSection parameter.

For Windows 2000, Windows XP, Windows Server 2003 and Windows 2008:

SharedSection uses the following format to specify the system and desktop heaps:
SharedSection=xxxx,yyyy,zzzz

For 32-bit operating systems, increase the yyyy value to "12288" and increase the
zzzz value to "1024".

For 64-bit operating systems, increase the yyyy value to "20480" and increase the
zzzz value to "2048" or "3072".

Refer to attached document for additional information.

These errors are caused by a reduction of resources available to the Window operating
system that cause a reduction in the RAM available for the non-interactive desktop
heaps. The reduced amount does not allow RIS sufficient RAM to spawn - which
create the errors.
Q> Moved Database and PDS Cannot Find Database

Moved database to a different machine with same domain name and now PDS won't
launch because it can't find the database.

The computers DNS cache needs to be updated to associate the new physical machine
with the appropriate IP address. To clear your DNS cache, perform the following
steps:

Click on Windows Start and enter cmd in the Start menu search text box.

1. Right-click Command Prompt and select Run as Administrator.

2. Run the following command:

ipconfig /flushdns

3. If the command succeeds, the system returns the following message:

Windows IP configuration successfully flushed the DNS Resolver Cache.

Q> Meaning of Schema Names

PD - Project Control Data. Contains the location of all drawings and the 2D reference
data.

PID - P&ID Task Schema. Contains information specific to each 2D PID drawing.

PIDM - P&ID Master Schema. Contains information posted from the PID schema.

PFD - PFD Task Schema. Contains information specific to each 2D PFD drawing.

PFDM - PFD Master Schema. Contains information posted from the PFD schema.

IN - IDM Task Schema. Contains information specific to each 2D Instrument and


associated devices.

INM - DM Master Schema. Contains information posted from the IN schema.

INR - IDM Reference Schema. Contains IDM reference data.

MTO - Material take off for MDP.


In addition to these schemas, there can be a backup schema for each of the schemas
listed above (PDBK, PIDBK, and so forth). The backup schemas can be used when
retrieving 2D data from an archives.

Q> Incompatible Gasket Error Matting RF and FF Flanged Ends

Trying to place a RF Flange with a FF Nozzle (Equipment) & we are


missing Gaskets at that joint.

Tried to add 21x11 & 11 combinations Gasket entries in PCD file, still the
Gasket is not getting generated. And the Error file also, do not show the
missing combination.

Set the alternate gasket.

PD_Shell -> (select project) -> Project Administrator -> Project Data
Manager -> Piping Model -> AREA -> DB NAME -> Revise Model Data
-> Material Takeoff -> Gasket Search (Alternate).