Loftus lies in Yorkshire, the largest of all England's counties. In the northwest of the county lies the Yorkshire Dales National Park, a lovely patchwork of limestone hills, gentle valleys and the high peaks of Whernside, Pen-y-ghent and Ingleborough. The classical Yorkshire Dales spread to the north from the market and spa towns of Settle, Skipton, Ilkley and Harrogate in North Yorkshire, with most of the larger southern dales such as Ribblesdale, Malhamdale and Airedale, Wharfedale and Nidderdale running roughly parallel from north to south, and the more northerly dales including Wensleydale, Swaledale and Teesdale running generally from west to east. The North York Moors is the county's other national park, with bleak upland moors and a magnificent rugged coastline. To the southeast of the region lie the Yorkshire Wolds, formed from chalk hills that arc from the Humber estuary west of Kingston upon Hull up to the North Sea coast between Bridlington and Scarborough.
Saltburn Smugglers Heritage Centre, Old Saltburn, Next to Ship Inn, Saltburn Tel: 01287 625252 The award winning Saltburn Smugglers is set in ancient fishermen's cottages, blending costumed characters with authentic sounds and smells. About 4 miles west of Loftus.
Captain Cook and Staithes Heritage Centre, High Street, Staithes Tel:01947 841454 The collection includes: Maritime, Natural Sciences, Personalities and Social History. Along with a complete recreation of Sanderson's shop, where a young Captain Cook was once an apprentice. About 5 miles east of Loftus.
Other Attractions - Durham Attractions Cumbria Attractions Lancashire Attractions Derbyshire Attractions Nottinghamshire Attractions Lincolnshire Attractions. Also see Loftus Loftus travel. Also Whitby hotels & Middlesbrough hotels.


Meh! Meh! Goats are busy on the farm, where they have many jobs. Some goats are raised for their wool, which can be made into clothing. Other goats are kept for their milk. Some goats help carry loads on the farm. In Goats, learn all about this useful animal.


We're so sorry to hear about your loss. May you find strength and comfort from the words of Psalms 34:18. It reads: "Jehovah is close to the brokenhearted; He saves those who are crushed in spirit." Our loving God is there for us if we ask for his help (1 John 5:14). He didn't intend for us to grow old and die. He thus has made the SURE promise of a resurrection RIGHT HERE ON EARTH when it is restored to a beautiful paradise (Psalms 37:9-11, 29; Acts 24:15; Isaiah 55;11). Can you see yourself welcoming back to life your loved ones? What a joy it will bring all of us. You can go online to JW.ORG and find out more about this resurrection.


Oracle Application Express is installed by default with Oracle Database 11g Release 1 (11.1) and later. This chapter describes required postinstallation configuration tasks for Oracle Application Express when installed with Oracle Database 12c or later in the standalone and multitenant architecture.
The instructions in this chapter apply to both new and upgrade installations. To learn more, see "Upgrading from a Previous Release of Oracle Application Express".
This chapter applies to installations in Oracle Database 12c in the multitenant architecture and non-CDB (or standalone) architecture. For more information on multitenant architecture, see "Part VI" in Oracle Database Concepts 12c Release 1 (12.1). For more information on different installation scenarios relating to Application Express in an Oracle Database 12c Release 1 (12.1) multitenant architecture, see Chapter 3, "Utilizing the Multitenant Architecture".
Upgrading to Oracle Database 12c Release 1 (12.1) will not patch Oracle Application Express. To learn more about downloading and installing Oracle Application Express from Oracle Technology Network (OTN) see "Downloading from Oracle Technology Network" in Oracle Application Express Installation Guide for Oracle Application Express release 4.2.
Review and satisfy all Oracle Application Express installation requirements. See "Oracle Application Express Installation Requirements".
Shut down any existing Oracle Database instances as well as Oracle-related processes.
Shut down any existing Oracle Database instances with normal or immediate priority, except for the database where you plan to install the Oracle Application Express schemas. On Oracle Real Application Clusters (Oracle RAC) systems, shut down all instances on each node.
If Oracle Automatic Storage Management (ASM) is running, shut down all databases that use ASM except for the database where you will install Oracle Application Express, and then shut down the ASM instance.
You can use the Windows Services utility, located either in the Windows Control Panel or from the Administrative Tools menu (under Start and then Programs), to shut down Oracle Database and ASM instances. Names of Oracle Databases are preceded with OracleService. The Oracle ASM service is named OracleASMService+ASM. In addition, shut down the OracleCSService service, which ASM uses. Right-click the name of the service and from the menu, choose Stop.
Back up the Oracle Database installation.
Oracle recommends that you create a backup of the current installation of Oracle Database installation before you install Oracle Application Express. You can use Oracle Database Recovery Manager, which is included the Oracle Database installation, to perform the backup.
Start the Oracle Database instance that contains the target database.
After backing up the system, you must start the Oracle instance that contains the target Oracle Database. Do not start other processes such as a Web listener. However, if you are performing a remote installation, make sure the Web listener for the remote database has started.
If you are connecting to a remote database, then start the Web listener.
In order to run, Oracle Application Express must have access to Oracle REST Data Services, Oracle HTTP Server and mod_plsql, or the embedded PL/SQL gateway. To learn more, see "About Choosing a Web Listener".
This section describes required postinstallation configuration tasks when running Oracle Application Express with Oracle REST Data Services.
Oracle Application Express automatically installs with Oracle Database 11g and later. To learn more about installing the Oracle Database, see the Oracle Database Installation Guide for your platform and "Recommended Pre-installation Tasks".
Note that the version.number in the file name reflects the current release number.
Copy the images directory, apex/images, from the Application Express software ZIP to a location on the file system where Oracle REST Data Services is installed.
Locate the installation guide for Oracle REST Data Services and follow instructions to complete installation and configuration steps.
For Oracle Database 12c multitenant architecture, ensure that you configure the connection using the service name of the specific pluggable database (PDB) you want to access. Do not use the service name of the CDB$ROOT unless you are configuring Oracle REST Data Services to address PDBs through the URL. See Oracle REST Data Services Installation and Developer Guide for more information.
In a new installation of Oracle Application Express, you configure RESTful Services by running the configuration script apex_rest_config.sql. This step is optional and only needs to be completed if you wish to use RESTful Services with Oracle REST Data Services on the instance. Once configured, the instance administrator can control the availability of the feature. If the instance administrator has disabled RESTful Services for this Application Express instance, RESTful Services are not available for this instance and the RESTful Services icon does not display. See "Configuring SQL Workshop" in Oracle Application Express Administration Guide.
RESTful Services requires Oracle REST Data Services release 2.0 or later.
Change your working directory to $ORACLE_HOME/apex.
When Prompted, enter a password for the APEX_LISTENER and APEX_REST_PUBLIC_USER accounts. When configuring RESTful Services in Oracle Application Express, it creates two new database accounts.
APEX_LISTENER - The account used to query RESTful Services definitions stored in Oracle Application Express.
APEX_REST_PUBLIC_USER - The account used when calling RESTful Services definitions stored in Oracle Application Express.
To run the examples described in this section, the compatible initialization parameter of the database must be set to at least 11.1.0.0.0. By default an Oracle Database 12c already has the parameter set properly, but a database upgraded to Oracle Database 12c from a prior version may not. See "Creating and Configuring an Oracle Database" in Oracle Database Administrator's Guide for information about changing database initialization parameters.
The examples below should be modified according to your environment and in a Oracle Database 12c multitenant architecture, should be run on each pluggable database (PDB).
The following example demonstrates how to grant connect privileges to any host for the APEX_040200 database user. This example assumes you connected to the database where Oracle Application Express is installed as SYS specifying the SYSDBA role.
-- the "connect" privilege if APEX_040200 does not have the privilege yet.
The following example demonstrates how to provide less privileged access to local network resources. This example is used to enable access to servers on the local host only, such as email and report servers.
Once the ACL has been fixed, you must run the first script in this section to apply the ACL to the APEX_040200 user. See "Granting Connect Privileges".
Oracle highly recommends you configure and use a Secure Sockets Layer (SSL) to ensure that passwords and other sensitive data are not transmitted in clear text in HTTP requests. Without the use of SSL, passwords could potentially be exposed, compromising security. SSL is an industry standard protocol that uses RSA public key cryptography in conjunction with symmetric key cryptography to provide authentication, encryption, and data integrity.
The Oracle Application Express interface is translated into German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese. A single instance of Oracle Application Express can be installed with one or more of these translated versions. At runtime, each user's Web browser language settings determine the specific language version.
The translated version of Oracle Application Express should be loaded into a database that has a character set that supports the specific language. If you attempt to install a translated version of Oracle Application Express into a database that does not support the character encoding of the language, the installation may fail or the translated Oracle Application Express instance may appear corrupt when run. The database character set AL32UTF8 supports all the translated versions of Oracle Application Express.
You can manually install translated versions of Oracle Application Express using SQL*Plus. The installation files are encoded in AL32UTF8.
Regardless of the target database character set, to install a translated version of Oracle Application Express, you must set the character set value of the NLS_LANG environment variable to AL32UTF8 before starting SQL*Plus.
In a multitenant architecture, the scripts below should be run in each pluggable database (PDB).
Whether you are installing for the first time or upgrading from a previous release, you must run the load_lang.sql script to run a translated version of Oracle Application Express.
The installation scripts are located in subdirectories identified by a language code in the $ORACLE_HOME/apex/builder. For example, the German version is located in apex/builder/de and the Japanese version is located in apex/builder/ja. Within each directory, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).
Where lang is the specific language (for example, load_de.sql for German or load_ja.sql for Japanese).
JOB_QUEUE_PROCESSES determine the maximum number of concurrently running jobs. In Oracle Application Express release 4.2, transactional support and SQL scripts require jobs. If JOB_QUEUE_PROCESSES is not enabled and working properly, you cannot successfully execute a script.
After installing or upgrading Oracle Application Express to release 4.2, you can view the number of JOB_QUEUE_PROCESSES in the installation log files. See "Reviewing a Log of an Installation Session".
You can also view the number of JOB_QUEUE_PROCESSES on the About Application Express page.
Log in to Oracle Application Express. See "Logging in to Your Oracle Application Express Workspace".
On the Administration list, click About Application Express.
The current number JOB_QUEUE_PROCESSES displays at the bottom of the page.
A workspace is a virtual private database allowing multiple users to work within the same Oracle Application Express installation while keeping their objects, data and applications private. Each workspace has a unique ID and name.
An Oracle Application Express administrator can create a workspace manually within Oracle Application Express Administration Services or have users submit requests. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance. See "Creating Workspaces" and "Managing Workspace Change Requests" in Oracle Application Express Administration Guide.
Log in to Oracle Application Express Administration Services. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance. You log in using the ADMIN account and password created or reset during the installation process.
In a Web browser, navigate to the Oracle Application Express Administration Services application.
hostname is the name of the system where Oracle REST Data Services is installed.
port is the port number assigned when configuring Oracle REST Data Services. In a default installation, this number is 8080. To learn more, see Oracle REST Data Services Installation and Developer Guide.
apex is the service name defined when configuring Oracle REST Data Services.
In Password, enter the Oracle Application Express administrator account password you specified when you installed Oracle Application Express.
See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.
Under Manage Workspaces, click Create Workspace.
The Create Workspace Wizard appears.
For Identify Workspace, enter a workspace name and description and click Next.
For Identify Schema, select the Oracle Forms application schema.
For Re-use existing schema, select Yes.
Select a schema from the list.
For Identify Administrator, enter the Workspace administrator information and click Next.
Log in to Oracle Application Express Administration Services as described in the previous section. See "Logging in to Oracle Application Express Administration Services" in Oracle Application Express Administration Guide.
Under Manage Workspaces, click Manage Developers and Users.
The Manage Developers and Users page appears.
The Create/Edit User page appears.
Under User Attributes, enter the appropriate information. Fields marked with an asterisk are required.
To learn more about a specific attribute, click the item label. When Help is available, the item label changes to red when you pass your cursor over it and the cursor changes to an arrow and question mark.
Under Password, type a case-sensitive password for this account.
If your organization has set up a password policy, be sure the password meets the requirements.
User is a developer - To add this user as a developer or Workspace administrator, select Yes. For end users, select No.
Developers can create and modify applications and database objects as well as view developer activity, session state, workspace activity, application, and schema reports.
User is a workspace administrator - To add this user as a Workspace administrator, select Yes. For developers or end users, select No.
In addition to having developer privileges, workspace administrators can create and edit user accounts, manage groups, alter passwords of users within the same workspace, and manage development services.
Account Availability - Select Unlocked to enable a user to log in to this account.
Require Change of Password on First Use - Select Yes to require the user to change the password immediately after logging in with the current, temporary password. Otherwise, select No.
Click Create User or Create and Create Another.
Once you create a workspace, you must log in to it using your login credentials (that is, the workspace name, user name, and password).
In a Web browser, navigate to the Oracle Application Express Login page.
port is the port number assigned when configuring the Oracle REST Data Services. In a default installation, this number is 8080. To learn more, see Oracle REST Data Services Installation and Developer Guide.
Workspace field - Enter the name of your workspace.
Username field - Enter your user name.
Password field - Enter your case-sensitive password.
Note that, depending on your setup, you might be required to change your password when you log in for the first time.
This section describes required post installation configuration tasks when running Oracle Application Express with the embedded PL/SQL gateway.
"About the Oracle Application Express Runtime Environment"
Oracle Application Express automatically installs with Oracle Database 11g and later. To learn more about installing the Oracle Database, see the Oracle Database Installation Guide for your operating environment and "Recommended Pre-installation Tasks".
In a new or upgrade installation, you load image and static resources into the XDB repository and make them available by running the configuration script apex_epg_config.sql.
Change your working directory to ORACLE_BASE\ORACLE_HOME\apex or whatever convention used to indicate the Oracle home.
Although the embedded PL/SQL gateway installs with the Oracle Database 12c, you must configure it before you can use it with Oracle Application Express. To accomplish this, you run a configuration script and unlock the ANONYMOUS account.
The Oracle XML DB Protocol Server with the embedded PL/SQL gateway is not supported before Oracle Database 11g.
In a new installation, you configure the embedded PL/SQL gateway by running the configuration script apxconf.sql. Then, you unlock the ANONYMOUS account.
If you are upgrading and have previously configured the embedded PL/SQL gateway, skip this section and go to "Enable Network Services in Oracle Database 12c".
If running in the Oracle Database 12c multitenant architecture, you only need to execute steps 5 and 6 once when configuring the first PDB, as you only need to unlock the ANONYMOUS account once in the root container.
Complete appropriate steps in sections "Enable Network Services in Oracle Database 12c" through "Create a Workspace and Add Oracle Application Express Users".
The embedded PL/SQL gateway runs in the Oracle XML DB Protocol Server in the Oracle Database. You can determine if the Oracle XML DB Protocol Server has HTTP enabled by verifying the associated port number.
If the port number returns 0, the Oracle XML DB Protocol Server is disabled.
To enable it, follow the instructions in "Enabling Oracle XML DB Protocol Server".
The embedded PL/SQL gateway runs in the Oracle XML DB Protocol Server in the Oracle Database.
"Accessing the Repository Using Protocols" and "Oracle XML DB Protocol Server Configuration Management" in Oracle XML DB Developer's Guide.
"Protocol Address Configuration" and "Port Number Limitations" in Oracle Database Net Services Reference.
The examples below should be modified according to your environment and in a 12c multitenant architecture, should be run on each pluggable database (PDB).
Oracle highly recommends you configure and use a Secure Sockets Layer (SSL) to ensure that passwords and other sensitive data are not transmitted in clear text in HTTP requests. Without the use of SSL, passwords could potentially be exposed, compromising security.
SSL is an industry standard protocol that uses RSA public key cryptography in conjunction with symmetric key cryptography to provide authentication, encryption, and data integrity.
The installation scripts are located in subdirectories identified by a language code in the unzipped distribution apex/builder. For example, the German version is located in apex/builder/de and the Japanese version is located in apex/builder/ja. Within each of directory, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).
An Oracle Application Express administrator can create a workspace manually within Oracle Application Express Administration Services or have users submit requests. Oracle Application Express Administration Services is a separate application for managing an entire Oracle Application Express instance. See "Creating Workspaces" and "Managing Workspace Requests" in Oracle Application Express Administration Guide.
hostname is the name of the system where Oracle XML DB Protocol Server is installed.
port is the port number assigned to HTTP on the Oracle XML DB Protocol Server. In a default installation, this number is 8080. If you are using the Oracle Database 12c multitenant architecture, then each pluggable database (PDB) will have a distinct port number.
apex is the database access descriptor (DAD) defined in the configuration file.
port is the port number assigned to HTTP on the Oracle XML DB Protocol Server. In a default installation, this number is 8080. If you are using the Oracle Database 12c multitenant architecture then each PDB will have a distinct port number.
For users who have upgraded from earlier releases, or who have a custom configuration, this value may be htmldb or something else. Verify your DAD with your Oracle Application Express administrator.
This section describes how to configure Oracle HTTP Server with mod_plsql distributed with Oracle Database 12c.
Within the context of this section, the Oracle home directory (ORACLE_HTTPSERVER_HOME) is the location where Oracle HTTP Server is installed.
You are using a version of Oracle Application Express that installs with Oracle Database 12c or later.
You are not upgrading from a previous release. This is a new installation of Oracle Application Express.
You are running Oracle HTTP Server distributed with Oracle Database 12c.
First, change the password for the Oracle Application Express ADMIN account. In the multitenant architecture, this should only be done in the pluggable database (PDB) to be configured and never in the CDB$ROOT container.
If you are upgrading from a prior release of Oracle Application Express, this step is unnecessary.
In the default profile in Oracle Database 12c, the parameter PASSWORD_LIFE_TIME is set to 180. If you are using Oracle Database 12c with Oracle Application Express, this causes the password for APEX_PUBLIC_USER to expire in 180 days. As a result, your Oracle Application Express instance will become unusable until you change the password.
To prevent this behavior, create another profile in which the PASSWORD_LIFE_TIME parameter is set to unlimited and alter the APEX_PUBLIC_USER account and assign it the new profile.
Oracle Database Security Guide for information on creating profiles and assigning them to database users.
Whether you are loading a new installation or upgrading from a previous release, you must copy the images directory from the top level of the apex\images directory to the location on the file system containing the Oracle home for Oracle HTTP Server.
During an upgrade, to ensure that you can revert to the previous version, rename your existing images directory for Oracle Application Express, indicating the release number of the images.
Oracle HTTP Server distributed Oracle9i Release 2—see the httpd.conf file.
Oracle Application Server 10g—see the marvel.conf or dads.conf files.
Oracle HTTP Server distributed with Oracle Database 11g or 12c —see the marvel.conf or dads.conf files.
When you locate the images directory path, rename the existing images directory to a backup location. Doing so enables you to revert to the previous release, if that becomes necessary.
You are running Oracle HTTP Server 12c.
Oracle HTTP Server is installed in an Oracle home.
Within the context of this document, ORACLE_HTTPSERVER_HOME is the location where Oracle HTTP Server is installed.
If this is a new installation of Oracle Application Express, you must edit the dads.conf file. The dads.conf file contains the information about the DAD to access Oracle Application Express.
Use a text editor and open the dads.conf.
In the examples above, ohs1 refers to the name of the Oracle HTTP Server instance. When running the Oracle HTTP Server Configuration Wizard, the default name is ohs1. It may have been changed to a name other than ohs1.
In the dads.conf file, replace ORACLE_HTTPSERVER_HOME, host, port, service_name, and apex_public_user_password with values appropriate for your environment. Note that the apex_public_user_password is the password you changed in "Change the Password for the APEX_PUBLIC_USER Database User". Also note that the service_name should be the service name of the PDB if configuring a multitenant architecture. It should never be the service_name of the CDB$ROOT container.
Note that the path listed is only an example. The path in the dads.conf file should reference the file system path described in "Copy the Images Directory". Also, if your are configuring an Oracle Application Express instance in a multitenant architecture, be sure to use the service name of the pluggable database (PDB) to be enabled. Never use the service name of the CDB$ROOT container.
Locate the line containing PlsqlNLSLanguage.
Save and exit the dads.conf file.
In a default installation, componentName is ohs1 but may have been changed when running the Oracle HTTP Server Configuration Wizard.
To run the examples described in this section, the compatible initialization parameter of the database must be set to at least 11.1.0.0.0. By default, Oracle Database 12c already has the parameter set properly, but a database upgraded to Oracle Database 12c from a prior version may not. See "Creating and Configuring an Oracle Database" in Oracle Database Administrator's Guide for information about changing database initialization parameters.
The examples below should be modified according to your environment and in an Oracle Database 12c multitenant architecture, should be run on each PDB.
Oracle highly recommends you configure and use Secure Sockets Layer (SSL) to ensure that passwords and other sensitive data are not transmitted in clear text in HTTP requests. Without the use of SSL, passwords could potentially be exposed, compromising security.
The PlsqlDatabasePassword parameter specifies the password for logging in to the database. You can use the dadTool.pl utility to obfuscate passwords in the dads.conf file.
To obfuscate passwords, run dadTool.pl by following the instructions in the dadTool.README file.
hostname is the name of the system where Oracle HTTP Server is installed.
port is the port number assigned to HTTP on the Oracle HTTP Server. In a default installation, this number is 7777.
pls is the indicator to use the mod_plsql cartridge.
apex is the database access descriptor (DAD) defined in the mod_plsql configuration file.
Be aware that if you change a port number, it is not updated in the portlist.ini file. You can only rely on this file immediately after installation.
Once you have verified that your upgrade installation was successful and all upgraded applications function properly, you should remove schemas from prior Oracle Application Express installations.
The database users associated with schemas from prior installations are privileged users and should be removed when they are no longer necessary. Removing schemas from a prior installation is a two step process. First you verify if a prior installation exists and then you remove the schemas.
If the results contain entries in the form FLOWS_XXXXXX or APEX_XXXXXX where XXXXXX represents six numbers, those entries are candidates for removal.
After following the instructions in"Remove Prior Oracle Application Express Installations", you may need to fix an invalid ACL if you are running Oracle Database 12c and you enabled network services for the prior Oracle Application Express schema.
The Oracle Application Express runtime environment enables you to run production applications. It includes only the packages necessary to run your applications, making it a more hardened environment. It does not provide a Web interface for administration.
You administer the Oracle Application Express runtime environment using SQL*Plus or SQL Developer and the APEX_INSTANCE_ADMIN API. To learn more see, "Managing a Runtime Environment" and in Oracle Application Express Application Builder User's Guide.
Follow the instructions in "Change the Password for the ADMIN Account".