ISS Technology Brief HP BladeSystem C3000 Enclosure Technologies, 2nd edition: Part 2
This is part two of a two part podcast of the ISS Technology Brief HP BladeSystem C3000 Enclosure Technologies, 2nd edition. This technology brief provides an overview of the HP BladeSystem C3000 Enclosure, Thermal Logic power and cooling technologies, and interconnect options.
I have xml files with with extension .ktr in subfolders
i want to replace the string <enclosure>"</enclosure> with <enclosure>^</enclosure>
i have written logic but it is not working correctly
sed -i '' 's#<enclosure>&\#x22;</enclosure>#<enclosure>&\#x5e;</enclosure>#g' *.ktr
... (3 Replies)
A simple question about the old c3000 ws
https://encrypted-tbn1.gstatic.com/images?q=tbn:ANd9GcQwJbws7Z2ALR0oCkw2emIv4lrJDDlbjRHUmIgd9VNA_i6Ej2CY
For shutdown correctly i use to press the power button,without do shutdown from cli first,is correct?
Or is better to shutdown(# shutdown -h now)... (2 Replies)
OCI_SET_EDITION(3)OCI_SET_EDITION(3)oci_set_edition - Sets the database editionSYNOPSIS
bool oci_set_edition (string $edition)
DESCRIPTION
Sets the database "edition" of objects to be used by a subsequent connections.
Oracle Editions allow concurrent versions of applications to run using the same schema and object names. This is useful for upgrading live
systems.
Call oci_set_edition(3) before calling oci_connect(3), oci_pconnect(3) or oci_new_connect(3).
If an edition is set that is not valid in the database, connection will fail even if oci_set_edition(3) returns success.
When using persistent connections, if a connection with the requested edition setting already exists, it is reused. Otherwise, a different
persistent connection is created
PARAMETERS
o $edition
- Oracle Database edition name previously created with the SQL " CREATE EDITION" command.
NOTES
Note
Oracle version requirement
This function is available from Oracle 11 gR2 onwards.
Caution
Persistent connections
To avoid inconsistencies and unexpected errors, do not use ALTER SESSION SET EDITION to change the edition on persistent connec-
tions.
Caution
DRCP Connection Pooling
To avoid inconsistencies and unexpected errors when using editions and DRCP with Oracle 11.2.0.1, keep a one-to-one correspondence
between the oci8.connection_class and the edition name used by applications. Each pooled server of a given connection class should
only be used with one edition. This restriction has been removed with Oracle 11.2.0.2.
RETURN VALUES
Returns TRUE on success or FALSE on failure.
EXAMPLES
Example #1
Two scripts can use different versions of myfunc() at the same time
<?php
// File 1
echo "Version 1 of application
";
oci_set_edition('ORA$BASE');
$c = oci_connect('hr', 'welcome', 'localhost/XE');
$s = oci_parse($c, "begin :r := myfunc(); end;");
oci_bind_by_name($s, ":r", $r, 20);
oci_execute($s);
echo "The result is $r
";
?>
<?php
// File 2
echo "Version 2 of application
";
oci_set_edition('E1');
$c = oci_connect('hr', 'welcome', 'localhost/XE');
$s = oci_parse($c, "begin :r := myfunc(); end;");
oci_bind_by_name($s, ":r", $r, 20);
oci_execute($s);
echo "The result is $r
";
?>
PHP Documentation Group OCI_SET_EDITION(3)