oci_set_action(3) [php man page]

OCI_SET_ACTION(3)														 OCI_SET_ACTION(3)

oci_set_action - Sets the action name

SYNOPSIS

       bool oci_set_action (resource  $connection, string  $action_name)

DESCRIPTION

	Sets the action name for Oracle tracing.

	The action name is registered with the database when the next 'roundtrip' from PHP to the database occurs, typically when an SQL statement
       is executed.

	The action name can subsequently be queried from database administration views such as V$SESSION. It can be used for tracing and  monitor-
       ing such as with V$SQLAREA and DBMS_MONITOR.SERV_MOD_ACT_STAT_ENABLE.

	The value may be retained across persistent connections.

PARAMETERS

	      o $connection
		-An Oracle connection identifier, returned by oci_connect(3), oci_pconnect(3), or oci_new_connect(3).

	      o $action_name
		- User chosen string up to 32 bytes long.

RETURN VALUES

	Returns TRUE on success or FALSE on failure.

EXAMPLES

       Example #1

	      Setting the action

	      <?php

	      $c = oci_connect('hr', 'welcome', 'localhost/XE');

	      // Record the action
	      oci_set_action($c, 'Friend Lookup');

	      // Code that causes a roundtrip, for example a query:
	      $s = oci_parse($c, 'select * from dual');
	      oci_execute($s);
	      oci_fetch_all($s, $res);

	      sleep(30);

	      ?>

	      // While the script is running, the administrator can see the actions
	      // being performed:

	      sqlplus system/welcome
	      SQL> select action from v$session;

NOTES

       Note

	      Oracle version requirement

	      This function is available when PHP is linked with Oracle Database libraries from version 10 g onwards.

       Tip

	      Performance

	      With  older  versions of OCI8 or the Oracle Database, the client information can be set using the Oracle DBMS_APPLICATION_INFO pack-
	      age. This is less efficient than using oci_set_client_info(3).

       Caution

	      Roundtrip Gotcha

	      Some but not all OCI8 functions cause roundtrips. Roundtrips to the database may not occur  with	queries  when  result  caching	is
	      enabled.

SEE ALSO

       oci_set_module_name(3), oci_set_client_info(3), oci_set_client_identifier(3).

PHP Documentation Group 													 OCI_SET_ACTION(3)

OCI_ROLLBACK(3) 														   OCI_ROLLBACK(3)

oci_rollback - Rolls back the outstanding database transaction

SYNOPSIS

       bool oci_rollback (resource  $connection)

DESCRIPTION

	Reverts all uncommitted changes for the Oracle $connection and ends the transaction. It releases all locks held. All Oracle SAVEPOINTS are
       erased.

	A transaction begins when the first SQL statement that changes data is executed with oci_execute(3)  using  the  OCI_NO_AUTO_COMMIT  flag.
       Further	data  changes made by other statements become part of the same transaction. Data changes made in a transaction are temporary until
       the transaction is committed or rolled back. Other users of the database will not see the changes until they are committed.

	When inserting or updating data, using transactions is recommended for relational data consistency and for performance reasons.

PARAMETERS

	      o $connection
		- An Oracle connection identifier, returned by oci_connect(3), oci_pconnect(3) or oci_new_connect(3).

RETURN VALUES

	Returns TRUE on success or FALSE on failure.

EXAMPLES

       Example #1

	      oci_rollback(3) example

	      <?php

	      // Insert into several tables, rolling back the changes if an error occurs

	      $conn = oci_connect('hr', 'welcome', 'localhost/XE');

	      $stid = oci_parse($conn, "INSERT INTO mysalary (id, name) VALUES (1, 'Chris')");

	      // The OCI_NO_AUTO_COMMIT flag tells Oracle not to commit the INSERT immediately
	      // Use OCI_DEFAULT as the flag for PHP <= 5.3.1.	The two flags are equivalent
	      $r = oci_execute($stid, OCI_NO_AUTO_COMMIT);
	      if (!$r) {
		  $e = oci_error($stid);
		  trigger_error(htmlentities($e['message']), E_USER_ERROR);
	      }

	      $stid = oci_parse($conn, 'INSERT INTO myschedule (startday) VALUES (12)');
	      $r = oci_execute($stid, OCI_NO_AUTO_COMMIT);
	      if (!$r) {
		  $e = oci_error($stid);
		  oci_rollback($conn);	// rollback changes to both tables
		  trigger_error(htmlentities($e['message']), E_USER_ERROR);
	      }

	      // Commit the changes to both tables
	      $r = oci_commit($conn);
	      if (!r) {
		  $e = oci_error($conn);
		  trigger_error(htmlentities($e['message']), E_USER_ERROR);
	      }

	      ?>

       Example #2

	      Rolling back to a SAVEPOINT example

	      <?php
	      $stid = oci_parse($conn, 'UPDATE mytab SET id = 1111');
	      oci_execute($stid, OCI_NO_AUTO_COMMIT);

	      // Create the savepoint
	      $stid = oci_parse($conn, 'SAVEPOINT mysavepoint');
	      oci_execute($stid, OCI_NO_AUTO_COMMIT);

	      $stid = oci_parse($conn, 'UPDATE mytab SET id = 2222');
	      oci_execute($stid, OCI_NO_AUTO_COMMIT);

	      // Use an explicit SQL statement to rollback to the savepoint
	      $stid = oci_parse($conn, 'ROLLBACK TO SAVEPOINT mysavepoint');
	      oci_execute($stid, OCI_NO_AUTO_COMMIT);

	      oci_commit($conn);  // mytab now has id of 1111
	      ?>

NOTES

       Note

	       Transactions are automatically rolled back when you close the connection, or when the script ends, whichever is soonest.  You  need
	      to explicitly call oci_commit(3) to commit the transaction.

	       Any  call  to  oci_execute(3)  that  uses  OCI_COMMIT_ON_SUCCESS mode explicitly or by default will commit any previous uncommitted
	      transaction.

	       Any Oracle DDL statement such as CREATE or DROP will automatically commit any uncommitted transaction.

SEE ALSO

       oci_commit(3), oci_execute(3).

PHP Documentation Group 													   OCI_ROLLBACK(3)