EXPUNGE (Project Administration)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : EXPUNGE (Project Administration)

Removes users who are accessing the Project, and releases claimed elements in Multiwrite databases.

This command can be used to remove phantom users after abnormal exits. Users who are actually accessing the Project will be removed as soon as they change module.

Note:

EXPUNGING users re moves them from the COMMS database but does not end their AVEVA E3D™ session or remove the file-locks on the database. To remove these locks you can use the Microsoft NETFILE API or proprietary tools like pstools from Sysinternals.

In a Global project, you can use this command on Constructor databases at Locations which you administering remotely by prefixing it with the REMOTE <loc> command, where <loc> is the Location identifier. See the REMOTE command for examples.

In a Global project, you can use the EXPUNGE DB SYSTEM command to expunge the current administered System database. You will have to give the ADMINISTER SYSTEM command first if you are administering a Location remotely.

Alternatively you can set the LCPOVW attribute to TRUE, which allows the daemon to overwrite locked files provided there are no database READERS (as recorded in the Session data in the COMMS database).

Note:

Do not use this facility if the project has users from other projects. Such users are valid database READERS but are not recorded in the Session data for the current project.

Examples:

EXPUNGE

Expunge all users. (This should be used with care.)

EXPUNGE ’29f’

Expunge user identified by given process number.

EXPUNGE USER ’USERA’

Expunge user given by name.

EXPUNGE USER nnnn

Expunges the specified user slot number.

EXPUNGE DB dbname USER usernumber

Expunges given user from given DB. This is allowed even if there are users accessing the DB. It is the preferred way of freeing unreleased claims.

EXPUNGE DB dbname

Releases elements which have been claimed in a multiwrite database. These elements may be inaccessible after a user has exited abnormally. This is not allowed if there are current users accessing the DB.

EXPUNGE DB SYSTEM

Releases elements which have been claimed in a SYSTEM database. These elements may be inaccessible after a user has exited abnormally.

EXPUNGE DAEMON

Expunge the Global daemon user (Global projects only). Note the EXPUNGE DAEMON command does not stop the Global daemon process. The Global daemon user is not expunged by default - however certain commands (such as MERGE CHANGES on a Transaction db) will fail if there is still a session for the Daemon user.

Command Syntax:


.-----<--------------------------------. / \| >-- EXPUNGE --*-- process_id --------------------------\| \| \| \|-- user ---------+-- username ----------\| \| \| \| \| ‘-- slot nnnn ---------\| \| \| \|-- DB dbname ----+-- USER usernumber ---\| \| \| \| \| ‘----------------------' \| \|-- DB SYSTEM ----. \| \| \|-- DB GLOBAL/DB -\| \| \| \|-- DAEMON -------\| \| \| ‘-----------------+----------------->

Note:

All the EXPUNGE syntax can be applied to a remote Location in a Global Project by prefixing the command by REMOTE <loc>, where <loc> is the Location identifier. See the REMOTE command for examples.

Querying:

Q ACTIVE

Related Commands:

SYSTAT,

For Global projects - REMOTE, REMOTE EXPUNGE