ODBC Server Reference Manual

Managing Customized Catalogs
HP NonStop ODBC Server Reference Manual—429151-002
7-7
Renaming ODBC or SQL Server Objects
Renaming ODBC or SQL Server Objects
When you customize or refresh a catalog, the NonStop ODBC Server assigns
ODBC/SQL Server names to the objects in the catalog not already registered in the
NonStop ODBC Server catalog.
How Names Are Assigned
When assigning ODBC/SQL Server object names, the NonStop ODBC Server usually
assigns the Guardian file name. For example, a table named
\TESS.$NOSS.PERSNL.EMPLOYEE is given the ODBC/SQL Server name
EMPLOYEE. Sometimes, however, the NonStop ODBC Server must assign a name
other than the Guardian file name. This situation usually occurs when a catalog
contains multiple objects that have the same file name but are in different subvolumes.
For example, four tables named EMPLOYEE (in different subvolumes) and three
tables named T1 could be registered in the catalog \TESS.$NOSS.PERSNL, as shown
in Figure 7-2.
USERCAT INSTALL would assign the tables different names and generate the
messages listed in Example 7-1
.
Figure 7-2. Tables With Duplicate Names Registered in One Catalog
Example 7-1. Name Mapping Warnings From USERCAT INSTALL
select "tdm: util usercat install \tess.$noss.persnl"
ODBC Server message 32652:
Object table \TESS.$NOSS.PERSNX.EMPLOYEE mapping to T_EMPLOYEE567490 added.
ODBC Server message 32652:
Object table \TESS.$NOSS.PERSNY.EMPLOYEE mapping to T_EMPLOYEE724838 added.
ODBC Server message 32652:
Object table \TESS.$NOSS.PERSNY.T1 mapping to T_T1809120 added.
ODBC Server message 32652:
Object table \TESS.$NOSS.PERSNZ.EMPLOYEE mapping to T_EMPLOYEE891245 added.
ODBC Server message 32652:
Object table \TESS.$NOSS.PERSNZ.T1 mapping to T_T1961851 added.
\tess.$noss.persnl
Catalog tables
EMPLOYEE
\tess.$noss.persnx
T1
EMPLOYEE
\tess.$noss.persny
T1
EMPLOYEE
\tess.$noss.persnz
T1
EMPLOYEE
VST045.vsd