= заметки по `oracle`
== остановка и запуск `apache`
{{{#!bash
sudo -u oracle /opt/oracle/product/apache/opmn/bin/opmnctl stopall
sudo -u oracle /opt/oracle/product/apache/opmn/bin/opmnctl startall
}}}

либо так:

{{{#!bash
sudo -s
su oracle
/opt/oracle/product/apache/Apache/Apache/bin/apachectl start (restart)
}}}

[[br]]
== `enterprise manager`
запуск:
{{{
#!bash
sudo su -l oracle
export TZ=Etc/GMT+6
/opt/oracle/product/10.2/bin/emctl start dbconsole
exit
}}}
[[br]]
после работы его лучше остановить, чтобы не жрал память:
{{{
#!bash
sudo -u oracle /opt/oracle/product/10.2/bin/emctl stop dbconsole
}}}

[[br]]
== перезапуск инстанса
{{{
#!bash
export ORACLE_SID=ftest10
( cat <<EOF
 connect / as sysdba
 shutdown abort;
 startup;
EOF
) | sqlplus /nolog
}}}

[[br]]
== toad debugger
пользователю оракла, под которым происходит отладка нужно дать привилегию:
{{{
#!sql
grant debug connect session to user;
}}}
[[br]]
а toad.exe добавить в исключения data execution prevention: панель управления - система - дополнительно - быстродействие - предотвращение выполнения данных - добавить - toad.exe

[[br]]
== если не работают отчёты sqlplus в терминале под windows 2003

=== Applies to ===

    * Oracle Server - Enterprise Edition - Version: 10.1.0.2.0 to 10.2.0.1.0
    * Oracle Server - Standard Edition - Version: 10.1.0.2.0 to 10.2.0.1.0
    * Microsoft Windows 2000
    * Microsoft Windows XP
    * Microsoft Windows Server 2003

=== Symptoms ===

When logged on to the Windows server as a non-Administrator OS account using Microsoft Terminal Services client (mstsc.exe), starting SQL*Plus fails with

    * SP2-1503: Unable to initialize Oracle call interface
    * SP2-0152: ORACLE may not be functioning properly

Starting SQL*Plus works when logged on to the Windows server using an Administrator OS account.

Starting SQL*Plus works when logged on locally to the Windows server console using the non-Administrator OS account.

==== Cause ====

The issue is related to a Windows Security configuration. The problem is caused by a security policy called "Create Global Objects". The user account that is used to run the program does not have the "Create global objects" user right. This security policy was introduced with Windows 2000 SP4, and determines if applications started during a Terminal Services session can create or access globally accessible memory. By default, members of the Administrators group, the System account, and Services that are started by the Service Control Manager are assigned the "Create global objects" user right.

==== Solution ====

Assign the "Create global objects" user right to the non-Administrator account.

1. Click Start, point to Programs, point to Administrative Tools, and then click Local Security Policy.
2. Expand Local Policies, and then click User Rights Assignment.
3. In the right pane, double-click Create global objects.
4. In the Local Security Policy Setting dialog box, click Add.
5. In the Select Users or Group dialog box, click the user account that you want to add, click Add, and then click OK.
6. Click OK.