Product: IESX
Version: GeoFrame 3.0
Application: Administration
Search Type: FAQ
Topic:
GeoFrame 'Command Line' commands and their functionality.
Description:
Solution:
The GeoFrame Project Manager handles tasks that have been issued from the
command line in a GeoFrame Xterm window. The GeoFrame Xterm is launched from
Geonet. Please be advised that some of these commands can be rather dangerous
to use. If you are not sure of exactly how to use any of these commands, please
call GeoQuest Customer Support.
1) gf_accounts
===========
Gives the user a listing of GeoFrame project names with relative Account name,
Baseline_account and date of last validation. At the end of the listing, it
will give a section on the different GeoFrame baseline accounts and a section
on any projects that are in a unusable state.
Example listing:
The GF projects on sgf3srvr are:
PROJECT_NAME ACCOUNT_NAME BASELINE_ACCOUNT LAST_VALIDATED
---------------------------------------------------------------------
aaaa_clone AAAA_CLONE GF3C0A_7B 07-JAN-98
aaaa_clone2 AAAA_CLONE2 GF3C0A_7B 12-APR-98
khp_paisley KHP_PAISLEY GF3C0A_7B 21-NOV-97
The GF catalog projects on sgf3srvr are:
PROJECT_NAME ACCOUNT_NAME BASELINE_ACCOUNT LAST_VALIDATED
---------------------------------------------------------------------
elvis ELVIS 08-JUN-98
gf3c0a_7b GF3C0A_7B 03-APR-98
These GF projects on sgf3srvr are in a unusable state:
If a project is unusable because its catalog is deleted,
you might try updating it to a new catalog account.
PROJECT_NAME ACCOUNT_NAME BASELINE_ACCOUNT LAST_VALIDATED
---------------------------------------------------------------------
JMASON1 GF3C0A_7B 09-FEB-98
TROY GF3C0A_7B 22-JUN-98
==============================================================================
2) proj_delete
===========
Type: proj_delete project_name project_password
Note: This command will not delete the directories/files of the project
on the UNIX level. It only deletes the project out of Oracle.
Deletion will have to be done manually through UNIX.
or
proj_delete project_name project_password -nospawn -force
Note: The -nospawn option deletes the project right away out of oracle.
The -force option deletes the project directories and files from
UNIX.
Run iesx_util, option 3 to delete the IESX project from the database.
==============================================================================
3) proj_changepasswd
=================
Allows the DBA or user to change the password of a project.
DBA Mode:
UNIX> setenv GF_PROJSYS_PASSW gf_sys (gf_sys being the default DBA password)
UNIX> proj_changepasswd ProjectAccName UserNewPassword Username
User Mode:
UNIX> proj_changepasswd ProjectAccName UserNewPassword [UserOldPassword] |
[Username]
================================================================================
4) proj_change_owner
=================
Allows the DBA to change the ownership of a GeoFrame project.
Example:
UNIX> setenv GF_PROJSYS_PASSW gf_sys (gf_sys being the default DBA password)
UNIX> proj_change_owner ProjectAccName NewOwnerName NewOwnerPassword
================================================================================
5) gf_users
========
Gives the user a listing of users that are currently running on the database.
This listing shows the Account_name or project name, the current user,
Client_id, Client_machine and process_id.
Example listing:
The current users on sgf3srvr are:
ACCOUNT_NAME CURRENT_USER CLIENT_ID CLIENT_MACHINE PROCESS_ID
----------------------------------------------------------------------------
DLC_TEST dlc 20081 natasha 20496
GF_PUBLIC khp 16681 ss-rockfish 1225
==============================================================================
6) proj_create
===========
Creates a project account to access your GeoFrame database. Caution is in
order as disks and projections are not created in project using this option.
ProMan will have to be used.
Example:
UNIX> proj_create project_name project_password baseline_account
==============================================================================
7) proj_delete
===========
Deletes a database project account. This will only delete GeoFrame projects -
not Charisma project, IESX or CPS-3 data associated with GeoFrame projects.
Use ProMan if your project contains Charisma, IESX or CPS-3 data. Make sure
that no one else is currently using the project you want to delete.
Example:
UNIX> proje_delete project_name project_password
==============================================================================
8) proj_import_baseline
====================
Imports the baseline database account. This command is run automatically
during installation. Make sure that no one else is currently using the
baseline.
Example:
UNIX> proj_import_baseline DmpFile CatalogAccName CatAccPassword -d gf3c0a_00 -pd on
==============================================================================
9) proj_complete_catalog
=====================
Imports the disk settings from one catalog and database to another catalog.
Optionally will enable/disable the ProMan private disk option. Make sure that
no one else is currently using the baseline.
Example:
UNIX> proj_complete_catalog CatalogAccName/Password dc gf3c0a_00 -pd on
==============================================================================
10) cleandb
=======
Deletes a catalog or project and, if a catalog is specified, all its projects
will be deleted. Bulk files will not be deleted. USE EXTREME CAUTION WITH
cleandb AS THIS SHOULD BE CONSIDERED ONLY AS A LAST RESORT DELETE.
Example:
UNIX> setenv FGS_USERID gf_dba/gf_dba
UNIX> cleandb catalog|project
=============================================================================
11) gn_gf_install
=============
Integrates GeoFrame applications in Geonet. You will have to have write
permission to the $GN_DIR/config, $GN_DIR/bin directories and resources.db
and gstab files in $GN_DIR/config. Make sure that no one else is currently
using the project or catalog.
==============================================================================
12) iesx_util_install.csh
=====================
This script will integrate the IESX utilities iesx_util, da_clear,
upgrade_10to_11 and iesx_patch in the Geonet directory.
Example:
UNIX> iesx_util_install.csh
================================================================================
13) pm_delprj
=========
Deletes the Charisma part of a GeoFrame project. This comand is used in the
event of an unsuccessful upgrade of a Charisma project from Charisma 3.8.3
to GeoFrame 3.0. It allows the GeoFrame project to be deleted without deleting
the bulk files used in Charisma. This is important when upgrading using the
in-place method for bulk files since it allows the project to be used in
Charisma 3.8.3. The rest of the project should be deleted using the delete
funciton in the ProMan when pm_deprj has finished. If the -keep_all option
is not used, all Charisma bulk data will be deleted
Example:
UNIX> setenv ORACLE_USERID gf_dba/gf_dba
UNIX> pm_delprj project_name -P -keep_all
================================================================================
14) free_space
==========
Gives a listing of the Oracle tablespace utilization and contiguous free
space. The maximum continuous space for TSDATA should be >3.2MB for catalog
import. Number of continuous space of 1 MB should be at least 1 and preferably
more for data and index.
Example:
UNIX> free_space $FGS_USERID or UNIX> free_space $SYSTEM_USERID
================================================================================
15) space_check.csh
===============
Gives a report of the Oracle tablespace utilization. Note, however, that this
does not show database tablespace fragmentation nor will it show if a Data File
is entirely full.
Example:
UNIX> space_check $SYSTEM_USERID
===============================================================================
16) defragment.csh
==============
Uses a script to defragment the Oracle Database.
This script exports the contents of your instance and destroys all tablespaces
and recreates them all from scratch and then imports the information back in.
This means you will need disk space for the export file and it will take the
time to recreate all table spaces. You should always make a full cold backup
before running this script. YOU MUST BE VERY CAREFUL UTILIZING THIS COMMAND.
===============================================================================
Last Modified on: 04-JAN-99