Databases Reference
In-Depth Information
"IN_CK" CHECK (pin_statspack in ('TRUE', 'FALSE')) ENABLE NOVALIDATE"
IMP-00003: ORACLE error 2264 encountered
ORA-02264: name already used by an existing constraint
…
. . importing table "STATS$WAITSTAT" 126 rows imported
…
About to enable constraints...
Import terminated successfully with warnings.
Now we are ready to run Statspack reports. Note that the script
spreport.sql
cannot be
used, since it only considers snapshots taken by the current instance. Instead, its companion
script
sprepins.sql
must be used. This latter script is called by
spreport.sql
once it has deter-
mined the database identifier and instance number. With
sprepins.sql
, setting both of these
figures is a manual process. When
sprepins.sql
is run, it lists the database instances in
STATS$DATABASE_INSTANCE
. Select the desired instance, preferably by copying and pasting.
SQL> @sprepins
Instances in this Statspack schema
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DB Id Inst Num DB Name Instance Host
----------- -------- ------------ ------------ ------------
4273840935 1 PRODDB IPROD dbserver3
Enter value for dbid: 4273840935
Using 4273840935 for database Id
Enter value for inst_num: 1
Using 1 for instance number
Completed Snapshots
Snap Snap
Instance DB Name Id Snap Started Level Comment
------------ ------------ ----- ----------------- ----- --------------
PR02 PROD 104 15 Aug 2006 16:30 10
…
202 22 Aug 2006 09:15 10
203 22 Aug 2006 09:30 10
At this point, the script asks for the beginning and ending snapshot identifiers and the
report file name in the usual manner. Once instance name and instance number have been
entered, there is no difference between reporting on snapshots captured by the current instance
and imported snapshot data.
