<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenText Analytics Database 26.2.x – Stored procedure functions</title>
    <link>/en/sql-reference/functions/stored-procedure-functions/</link>
    <description>Recent content in Stored procedure functions on OpenText Analytics Database 26.2.x</description>
    <generator>Hugo -- gohugo.io</generator>
    
	  <atom:link href="/en/sql-reference/functions/stored-procedure-functions/index.xml" rel="self" type="application/rss+xml" />
    
    
      
        
      
    
    
    <item>
      <title>Sql-Reference: ACTIVE_SCHEDULER_NODE</title>
      <link>/en/sql-reference/functions/stored-procedure-functions/active-scheduler-node/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/stored-procedure-functions/active-scheduler-node/</guid>
      <description>
        
        
        &lt;p&gt;Returns the &lt;a href=&#34;../../../../en/extending/stored-procedures/executing-stored-procedures/triggers/scheduled-execution/&#34;&gt;active scheduler node&lt;/a&gt;. A &lt;a href=&#34;../../../../en/sql-reference/statements/create-statements/create-schedule/&#34;&gt;schedule&lt;/a&gt; must be associated with a &lt;a href=&#34;../../../../en/sql-reference/statements/create-statements/create-trigger/&#34;&gt;trigger&lt;/a&gt; to be enabled.&lt;/p&gt;
&lt;p&gt;To view existing schedules, see &lt;a href=&#34;../../../../en/sql-reference/system-tables/v-catalog-schema/user-schedules/#&#34;&gt;USER_SCHEDULES&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../en/sql-reference/statements/select/#&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../en/glossary/volatile-functions/&#34; title=&#34;&#34;&gt;Volatile&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;ACTIVE_SCHEDULER_NODE()
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;Superuser&lt;/p&gt;

&lt;h2 id=&#34;examples&#34;&gt;Examples&lt;/h2&gt;
&lt;p&gt;To return the active scheduler node:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT active_scheduler_node();

 active_scheduler_node
-----------------------
 initiator
(1 row)
&lt;/code&gt;&lt;/pre&gt;
      </description>
    </item>
    
    <item>
      <title>Sql-Reference: ENABLE_SCHEDULE</title>
      <link>/en/sql-reference/functions/stored-procedure-functions/enable-schedule/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/stored-procedure-functions/enable-schedule/</guid>
      <description>
        
        
        &lt;p&gt;Enables or disables a schedule. A schedule can only be enabled if a trigger is attached to it.&lt;/p&gt;
&lt;p&gt;To view existing schedules, see &lt;a href=&#34;../../../../en/sql-reference/system-tables/v-catalog-schema/user-schedules/#&#34;&gt;USER_SCHEDULES&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../en/sql-reference/statements/select/#&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../en/glossary/volatile-functions/&#34; title=&#34;&#34;&gt;Volatile&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;ENABLE_SCHEDULE ( &amp;#39;[[&lt;span class=&#34;code-variable&#34;&gt;database.&lt;/span&gt;]&lt;span class=&#34;code-variable&#34;&gt;schema.&lt;/span&gt;]&lt;span class=&#34;code-variable&#34;&gt;schedule&lt;/span&gt;&amp;#39;, &lt;span class=&#34;code-variable&#34;&gt;enabled&lt;/span&gt; )
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;arguments&#34;&gt;Arguments&lt;/h2&gt;
&lt;dl&gt;
&lt;dt&gt;&lt;code&gt;[&lt;/code&gt;&lt;em&gt;&lt;code&gt;database&lt;/code&gt;&lt;/em&gt;&lt;code&gt;.]&lt;/code&gt;&lt;em&gt;&lt;code&gt;schema&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;&lt;p&gt;Database and &lt;a href=&#34;../../../../en/admin/configuring-db/designing-logical-schema/using-multiple-schemas/setting-search-paths/&#34;&gt;schema&lt;/a&gt;. The default schema is &lt;code&gt;public&lt;/code&gt;. If you specify a database, it must be the current database.&lt;/p&gt;
&lt;/dd&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;schedule&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;The schedule to enable or disable.&lt;/dd&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;enabled&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;Boolean, whether to enable the trigger.&lt;/dd&gt;
&lt;/dl&gt;
&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;Superuser&lt;/p&gt;

&lt;h2 id=&#34;examples&#34;&gt;Examples&lt;/h2&gt;
&lt;p&gt;To enable a schedule:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT enable_schedule(&amp;#39;vmart.management.daily_1am&amp;#39;, true);
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;To disable a schedule:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT enable_schedule(&amp;#39;vmart.management.daily_1am&amp;#39;, false);
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;If you leave the database and schema empty, the default is &lt;em&gt;&lt;code&gt;current_database&lt;/code&gt;&lt;/em&gt;.public:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT enable_schedule(&amp;#39;biannual_22_noon_gmt&amp;#39;, true);
&lt;/code&gt;&lt;/pre&gt;
      </description>
    </item>
    
    <item>
      <title>Sql-Reference: ENABLE_TRIGGER</title>
      <link>/en/sql-reference/functions/stored-procedure-functions/enable-trigger/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/stored-procedure-functions/enable-trigger/</guid>
      <description>
        
        
        &lt;p&gt;Enables or disables a trigger.&lt;/p&gt;
&lt;p&gt;To view existing triggers, see &lt;a href=&#34;../../../../en/sql-reference/system-tables/v-catalog-schema/stored-proc-triggers/#&#34;&gt;STORED_PROC_TRIGGERS&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../en/sql-reference/statements/select/#&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../en/glossary/volatile-functions/&#34; title=&#34;&#34;&gt;Volatile&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;ENABLE_TRIGGER ( &amp;#39;[[&lt;span class=&#34;code-variable&#34;&gt;database.&lt;/span&gt;]&lt;span class=&#34;code-variable&#34;&gt;schema.&lt;/span&gt;]&lt;span class=&#34;code-variable&#34;&gt;trigger&lt;/span&gt;&amp;#39;, &lt;span class=&#34;code-variable&#34;&gt;enabled&lt;/span&gt; )
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;arguments&#34;&gt;Arguments&lt;/h2&gt;
&lt;dl&gt;
&lt;dt&gt;&lt;code&gt;[&lt;/code&gt;&lt;em&gt;&lt;code&gt;database&lt;/code&gt;&lt;/em&gt;&lt;code&gt;.]&lt;/code&gt;&lt;em&gt;&lt;code&gt;schema&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;&lt;p&gt;Database and &lt;a href=&#34;../../../../en/admin/configuring-db/designing-logical-schema/using-multiple-schemas/setting-search-paths/&#34;&gt;schema&lt;/a&gt;. The default schema is &lt;code&gt;public&lt;/code&gt;. If you specify a database, it must be the current database.&lt;/p&gt;
&lt;/dd&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;trigger&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;The trigger to enable or disable.&lt;/dd&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;enabled&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;Boolean, whether to enable the trigger.&lt;/dd&gt;
&lt;/dl&gt;
&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;Superuser&lt;/p&gt;

&lt;h2 id=&#34;examples&#34;&gt;Examples&lt;/h2&gt;
&lt;p&gt;To enable a trigger:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT enable_trigger(&amp;#39;vmart.management.log_user_actions&amp;#39;, true);
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;To disable a trigger:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT enable_trigger(&amp;#39;vmart.management.log_user_actions&amp;#39;, false);
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;If you leave the database and schema empty, the default is &lt;em&gt;&lt;code&gt;current_database&lt;/code&gt;&lt;/em&gt;.public:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT enable_trigger(&amp;#39;revoke_log_privileges&amp;#39;, true);
&lt;/code&gt;&lt;/pre&gt;
      </description>
    </item>
    
    <item>
      <title>Sql-Reference: EXECUTE_TRIGGER</title>
      <link>/en/sql-reference/functions/stored-procedure-functions/execute-trigger/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>/en/sql-reference/functions/stored-procedure-functions/execute-trigger/</guid>
      <description>
        
        
        &lt;p&gt;Manually executes the stored procedure attached to a trigger. This is generally used for testing the trigger.&lt;/p&gt;
&lt;p&gt;To view existing triggers, see &lt;a href=&#34;../../../../en/sql-reference/system-tables/v-catalog-schema/stored-proc-triggers/#&#34;&gt;STORED_PROC_TRIGGERS&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is a meta-function. You must call meta-functions in a top-level &lt;a href=&#34;../../../../en/sql-reference/statements/select/#&#34;&gt;SELECT&lt;/a&gt; statement.&lt;/p&gt;

&lt;h2 id=&#34;behavior-type&#34;&gt;Behavior type&lt;/h2&gt;
&lt;a class=&#34;glosslink&#34; href=&#34;../../../../en/glossary/volatile-functions/&#34; title=&#34;&#34;&gt;Volatile&lt;/a&gt;
&lt;h2 id=&#34;syntax&#34;&gt;Syntax&lt;/h2&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;EXECUTE_TRIGGER ( &amp;#39;[[&lt;span class=&#34;code-variable&#34;&gt;database.&lt;/span&gt;]&lt;span class=&#34;code-variable&#34;&gt;schema.&lt;/span&gt;]&lt;span class=&#34;code-variable&#34;&gt;trigger&lt;/span&gt;&amp;#39; )
&lt;/code&gt;&lt;/pre&gt;&lt;h2 id=&#34;arguments&#34;&gt;Arguments&lt;/h2&gt;
&lt;dl&gt;
&lt;dt&gt;&lt;code&gt;[&lt;/code&gt;&lt;em&gt;&lt;code&gt;database&lt;/code&gt;&lt;/em&gt;&lt;code&gt;.]&lt;/code&gt;&lt;em&gt;&lt;code&gt;schema&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;&lt;p&gt;Database and &lt;a href=&#34;../../../../en/admin/configuring-db/designing-logical-schema/using-multiple-schemas/setting-search-paths/&#34;&gt;schema&lt;/a&gt;. The default schema is &lt;code&gt;public&lt;/code&gt;. If you specify a database, it must be the current database.&lt;/p&gt;
&lt;/dd&gt;
&lt;dt&gt;&lt;em&gt;&lt;code&gt;trigger&lt;/code&gt;&lt;/em&gt;&lt;/dt&gt;
&lt;dd&gt;The trigger to execute.&lt;/dd&gt;
&lt;/dl&gt;
&lt;h2 id=&#34;privileges&#34;&gt;Privileges&lt;/h2&gt;
&lt;p&gt;Superuser&lt;/p&gt;

&lt;h2 id=&#34;examples&#34;&gt;Examples&lt;/h2&gt;
&lt;p&gt;To execute a trigger:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT execute_trigger(&amp;#39;vmart.management.log_user_actions&amp;#39;);
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;If you leave the database and schema empty, the default is &lt;em&gt;&lt;code&gt;current_database&lt;/code&gt;&lt;/em&gt;.public:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;=&amp;gt; SELECT execute_trigger(&amp;#39;revoke_log_privileges&amp;#39;);
&lt;/code&gt;&lt;/pre&gt;
      </description>
    </item>
    
  </channel>
</rss>
