下载文档原格式
This guide describes how to quickly power on and boot Oracle’s SPARC T4-2server for the first time using the preinstalled Oracle Solaris Operating System (Oracle Solaris OS).Detailed installation information can be found in the SPARC T4-2Server Installation Guide ,which is available at the Oracle documentation web site:/docs/cd/E23075_01Shipping ContentsSafety and Compliance InformationBefore performing an installation,refer to the following documents for safety information regarding the SPARC T4-2server:■Important Safety Information for Sun Hardware Systems -Printed document included in the shipping kit.■SPARC T4-2Server Safety and Compliance Manual -Available online at the Oracle documentation web site.QuantityItem1Server2AC power cords1RJ-45to DB-9crossover adapter 1Antistatic wrist strap 1Rail rackmounting kit 1Cable management arm Various documentsSPARC T4-2 ServerGetting Started Guide▼Install Optional ComponentsBefore installing the server into the rack,you must first install any optional components that you ordered with the server,such as DIMMs and PCIe cards.Refer to the SPARC T4-2Server Service Manual for instructions on installing optional components.▼Prepare to Install the ServerSetting up the server for the first time takes about45to75minutes.Plan for additional time if you are also installing optional hardware and rackmounting kits.Caution–Do not apply power until instructed to do so.–This system includes a service processor (SP)that is used to configure and boot the host server.To properly configure the host server and view SP messages,do not apply AC power to the server until the SP and host networking connections are made,as described in this guide.1.Choose the best way to set up the server for your environment.The instructions in this guide work for any networking environment and require a terminal device for connecting to a serial port.If you have a networking environment running DHCP,you can configure your system using the Ethernet management port by following the instructions in the installation guide.2.Obtain a terminal device.You configure the server through the SP using the built-in serial and network management ports,not through a graphical interface and keyboard.To communicate with the SP,you need a terminal device,which can be a terminal,a terminal server,or a laptop running terminal emulation software.3.Gather your configuration information.Refer to the installation guide for a checklist.▼Install the ServerFor quick installation and configuration,follow these steps.For more detailed information,refer to the complete online product documentation set.1.Confirm that you received all the parts needed for setting up the server.See“Shipping Contents”for details.2.Place the server in its intended location.For rackmounting instructions,refer to the installation guide.3.Connect a serial cable between the server’s SER MGT port and a terminal device.This connection provides the initial communication with the SP.Set up the server to communicate using9600baud,8bit,no parity,1stop bit.For DTE-to-DTEcommunication,use the supplied RJ-45crossover adapters with a standard RJ-45cable to set up a null modem configuration so that the transmit and receive signals are crossed over.FIGURE1Server Connections4.(Optional)Connect an Ethernet cable between the server’s NET MGT port and the network to whichfuture connections to the SP and host will be made.Configure the system for the first time through the SER MGT port.After the initial configuration,you can set up communication between the SP and host through this Ethernet interface.5.Connect an Ethernet cable between one of the server’s NET ports and the network to which the serverwill communicate.6.Connect the power cords to the power supplies and to separate power sources.If your server is equipped with two power supplies,connect them to separate power sources to provide power redundancy.The system can operate with one power connection,but having only one power source reduces the redundancy.When the power cords are connected,the SP initializes and the power supply LEDs illuminate.After a few minutes,the SP login prompt displays on the terminal device.At this time,the host is not initialized or powered on.7.At the terminal device,log in to the SP as root with a password of changeme .After a brief delay,the Oracle Integrated Lights Out Manager (Oracle ILOM)prompt (->)is displayed.For optimal security,change the root password.Refer to the Oracle ILOM documentation for more information about administration tasks such as changing passwords,adding accounts,and setting account privileges.Note –By default,the SP is configured to use DHCP to obtain an IP address.If instead you plan to assign astatic IP address to the SP,refer to the installation guide for instructions.8.Power on the server and redirect the host output to display on the serial terminal device.The server initialization takes approximately 20minutes to complete.9.When prompted,follow the onscreen instructions and type the configuration information for your system.If you are not sure how to respond,accept the default and make changes later when the Oracle Solaris OS is running.After you confirm the configuration information,the server reboots and displays the Oracle Solaris login prompt.10.Log in to the server.Use the following commands to display information about the system:■showrev –Displays the host name and system architecture e the -a option to display the patches that are installed.■psrinfo –Displays information about the number and status of the processors and cores in the host.Refer to the Oracle Solaris OS man pages and documentation for more details about these commands.▼Check for Latest Patches and FirmwareLater versions of OS patches and server firmware might be available for your server.Some server features are enabled only when certain versions of patches or firmware are installed.Refer to the SPARC T4-2Server Product Notes for details about required versions and patches.For updates,go to the My Oracle Support web site:https://SUNSP00144FAC732F login:root Password:changeme . . .->->start /SYSAre you sure you want to start /SYS (y/n)?y ->start /HOST/consoleAre you sure you want to start /HOST/CONSOLE (y/n)?y Serial console started.. . .Related DocumentationFeedbackProvide feedback on this document at:/goto/docfeedbackSupport and AccessibilityDocumentationLinksAll Oracle products /documentationSPARC T4-2server /docs/cd/E23075_01Oracle ILOM/docs/cd/E19860-01Oracle Solaris and other system software/technetwork/indexes/documentation/#sys_swDescriptionLinksAccess electronic support through My Oracle Support.https:// For hearing impaired:/accessibility/support.html Learn about Oracle’s commitment to accessibility./us/corporate/accessibilityCopyright©2011,Oracle and/or its affiliates.All rights reserved. Copyright©2011,Oracle et/ou ses affiliés.Tous droits réservés.Part Number: E23081-02Mfg. Number: 7015567November 2011。
Protecting business-critical data stored in Oracle databases while keepingthat data online and available is easier when you have a solution with a plug-in specifically designed for Oracle. With Quest® NetVault Backup, you’ll be able to take full advantage of the world’s leading relational database management system. NetVault Backup gives you confidence that you can recover your Oracle environments, including Oracle Real Application Clusters (RAC) and Data Guard, while eliminating the need for complex scripting. Through an intuitive user interface and automated workflow processes, NetVault Backup offers a centralized console to help you set up, configure and define backup and restore policies for all your Oracle databases. Plus, you have the flexibility to select your preferred backup method without having to learn Oracle database internals, thanks to support for online backups via simple user-managed or full-featured Recovery Manager (RMAN) backups. NetVault Backup also offers granular control that minimizes downtime, providing youwith faster and more reliable backups and restores of complete databases, individual tablespaces or individual datafiles. Through automatic integration with a wide range of backup devices, you can be confident that your Oracle data is protected and safely stored off site to meet your disaster recovery and business continuity goals.NetVault Backup supports important features such as Oracle RAC, Data Guard, Automated Storage Management (ASM), Flashback Database and Transparent Data Encryption, and offers you advanced backup and recovery options in case of hardware failure or data loss. Protect your business-critical Oracle data with confidence and agility.NetVault Backup for OracleAward-winning protection for business-critical data stored in Oracle databasesBENEFITS:• User-managed or RMAN-basedonline backups• Support for RMAN compression• Protection for single-instance,multi-instance RAC and DataGuard environments• Protection for Oracle datain third-party (non-RAC)clustered environments• Backup Parameter, Control,Archived Redo Log Files andExternal Configuration Files• Protection down to datafile levels• Automatic instance configuration• Point-and-click graphic userinterface (GUI)KEY BENEFITSReduce risk with flexible backup and recovery — NetVault Backup gives you tools to simplify backup and recovery of business-critical Oracle databases. With NetVault Backup, you can create a comprehensive and flexible backup policy without the need to understand Oracle database internals. You have the flexibility to choose between simple user-managed or full-featured RMAN-based backups. Through point-and-click automated options, NetVault Backup reduces reliance on human interaction, which eliminates syntax errors caused by manual intervention.Minimize downtime by speeding uprestores (restore only what is needed) — NetVault Backup ensures databases remain online and fully accessible during backup operations, ensuring no user downtime. Integration withOracle’s Flashback Database maximizes availability by enabling you to rewind to a previous time to correct problems caused by logical data corruptions or user errors without restoring physical datafiles. When needed, you can perform full, incremental, and time-, SCN- and log sequence number-based, point-in-time restores. NetVault Backup is designedfor granular recoveries, enabling you to recover complete databases, individual tablespaces or individual datafiles.Increase business continuity through automatic integration with a widerange of backup devices — With off-site backups being an important part of the data protection plan for business-critical applications, NetVault Backup integrates with a wide range of storage devices, enabling you to store backup data on disk, in a virtual tape library (VTL) or on tape.ABOUT QUESTQuest helps our customers reducetedious administration tasks so they can focus on the innovation necessary for their businesses to grow. Quest® solutions are scalable, affordable and simple-to-use, and they deliver unmatched efficiency and productivity. Combined with Quest’s invitation to the global community to be a part of its innovation, as well as our firm commitment to ensuring customer satisfaction, Quest will continue to accelerate the delivery of the mostcomprehensive solutions for Azure cloud management, SaaS, security, workforcemobility and data-driven insight.Quest, NetVault and the Quest logo are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit /legal/trademark-information.aspx. All other trademarks and registered trademarks are property of their respective owners.© 2017 Quest Software Inc. ALL RIGHTS RESERVED.DataSheet-NVBU4Oracle-US-KS-25712Quest4 Polaris Way, Aliso Viejo, CA 92656 | If you are located outside North America, you can find local office information on our Web site.。
ORA-09751: pw_attachPorts: 服务器调用pws_attach 失败ORA-09752: pw_attachPorts: port_allocate 失败ORA-09753: spwat: 无效的进程号ORA-09754: sppst: 传送给sppst 的进程号无效ORA-09755: osngpn: 端口配置失败ORA-09756: osnpns: 名服务器中没有端口ORA-09757: osnipn: 端口配置失败ORA-09758: osnipn: 无法检查名服务器中的端口ORA-09759: osnsbt: 收到的信息错误ORA-09760: osnpui: 无法发送中断信息ORA-09761: pw_destroyPorts: 服务器调用pws_stop_instance 失败ORA-09762: sNeXT_instanceName: 转换错误ORA-09763: osnmpx: 交换Mach 端口时出现发送/接收错误ORA-09764: osnmop: oracle 可执行（代码）访问错误ORA-09765: osnmop: 分叉失败ORA-09766: osnmop: 缓冲区分配失败ORA-09767: osnmfs: msg_send 的返回代码错误ORA-09768: osnmgetmsg: 无法读信息ORA-09769: osnmbr: 无法发送中断信息ORA-09770: pws_look_up: 转换失败ORA-09771: osnmwrtbrkmsg: msg_send 的返回代码错误ORA-09772: osnpmetbrkmsg: 来自主机的信息类型错误ORA-09773: osnmgetdatmsg: 来自主机的信息类型错误ORA-09774: osnmui: 无法发送中断信息ORA-09775: osnmrs: 重置协议错误ORA-09776: pws_look_up: (Oracle 帮助程序) 可执行(代码) 访问错误ORA-09777: osnpbr: 无法发送中断信息ORA-09778: snynfyport: 无法配置通知端口ORA-09779: snyGetPort: 无法分配端口ORA-09786: sllfop: 打开错误，无法打开文件ORA-09787: sllfop: 不可识别的处理选项，格式错误ORA-09788: sllfrb: 无法读文件ORA-09789: sllfsk: 无法读文件ORA-09790: sllfcf: 无法关闭文件ORA-09791: slembdf: 转换错误，无法转换错误文件名ORA-09792: sllfop: 无法分配读缓冲区ORA-09793: szguns: 用户名的长度大于缓冲区的长度ORA-09794: szrbuild: 角色名的长度大于缓冲区的长度ORA-09795: szrbuild: 无法malloc 角色结构ORA-09796: szrbuild: 无法malloc 角色名ORA-09797: 无法获得O/S MAC 权限ORA-09798: 标记比较失败ORA-09799: 文件标记检索失败ORA-09800: 进程阅读权限标记检索失败。
MY ORACLE SUPPORTPersonalize your support experience with My Oracle Support—our award-winning Web portal that offers you secure, anytime access to Oracle expertise. Only from Oracle.Key benefits •Personalized knowledge •Proactive problem detection •Collaborate support communitiesKey customer results •97% of issues resolved through the knowledgebase •40% faster service request resolution•30% faster service request creation•25% problem avoidance Increase productivity with a personalized view of information specific to your Oracle environment. Resolve issues faster with embedded configuration management capabilities. Reduce IT risks and costs with real-time insight into Oracle knowledge articles that are relevant to your systems. Maximize system availability with proactive Security & Product Alerts, Patch Advice and Health Checks. My Oracle Support—our exclusive Web portal—offers you immediate, secure access to the critical information you need for a superior support experience, only from Oracle Premier Support.Next Generation Support ExperienceTwo award winning platforms, Oracle MetaLink and Oracle Software Configuration Manager have been combined to bring you unprecedented personalized, proactive and collaborative support capabilities in one simplified platform. Using Web 2.0 technologies, these industry leading enhancements make your interactions with Oracle Support faster and more efficient. With details of your Oracle configurations securely shared with Oracle support, your issues are resolved faster and Oracle is able to proactively notify you of possible issues before they impact your business. My Oracle Support, our exclusive Web support portal, provides instant access to the latest support information, forums, communities, security, and product alerts —all included as part of your annual Oracle Premier Support subscription. When you leverage My Oracle Support, expect a superior support experience.Personalized KnowledgeWith its easy and intuitive navigation, My Oracle Support provides a simplified and personalized dashboard representing all of your systems activity and Oracle Support interactions. You have access to a personalized view of topics and content relevant to your specific applications and areas of interest. The PowerView feature allows for advanced filtering and customization for easier and rapid access to configuration data, knowledge documents, and proactive product alerts-- increasing productivity and helping to resolve issues quickly. With embedded configuration management capabilities you are able to seamlessly integrate your Oracle configuration information into the service request flow accelerating service request resolution.Oracle support engineers use secure, centralized access to your configuration to more quickly diagnose and resolve your critical issues and to help you avoid problems. By taking advantage of the configuration management features to make sure you have the latest security and product alerts for your specific configurations, you benefit from improved system stability.The Oracle knowledgebase holds more than 500,000 solutions, covering more than 1,250 products, which successfully address 97 percent of customer inquiries.Access threaded discussions about hundreds of topics in our online customer forums. You can also share your knowledge and expertise with the Oracle community and gain knowledge from other users by submitting documents through our Customer Knowledge Exchange.My Oracle Support provides the comprehensive tools you need to most effectively track, manage and support your Oracle environments.Worldwide Headquarters500 Oracle ParkwayRedwood Shores, CA94065 U.S.A.Worldwide InquiriesPhone+1.650.506.7000+1.800.ORACLE1Fax+1.650.506.7200 Proactive Problem DetectionMy Oracle Support is your portal to the most comprehensive and integrated Oracle product, technology, and support information across the industry. By aligning your Oracle system details to the extensive knowledge base of over 500,000 problem resolutions, spanning 1,250 products, you can prevent known issues from affecting your systems. Avoid unnecessary downtime and drive greater system stability with My Oracle Support.Security & Product Alerts, Patch Advice and Health Checks specific to your environment proactively notify you of potential system issues and provide recommendations that help you improve system performance and offer you greater control over your Oracle environment. This ongoing information exchange between Oracle and your enterprise systems automates labor-intensive tasks and significantly reduces IT-infrastructure risks and costs, making system changes easier to manage.Collaborative Support SolutionsYour access to Oracle product and technology expertise is greatly expanded when you tap into a global network of trusted resources. Interactive features enable real-time exchange of best practices and industry knowledge with your technical peers in areas that align to your IT challenges. Built on Oracle’s Web 2.0 technology, My Oracle Support offers multiple community channels from discussion forums, document exchange, tagging, people finder, and RSS feeds—allowing you to stay informed about the key topics that matter most. This collaborative and interactive experience is an area of continued investment for Oracle bringing you a forum to interact with industry peers for faster problem resolution and proactive problem avoidance.Experience Next Generation SupportYour Oracle solutions help you maintain a competitive business advantage. To get the most out of your Oracle solutions and ensure maximum system availability, you need more. You need My Oracle Support, your one-stop portal for easy access to the information needed to minimize risks and drive maximum system availability. It’s more than support as you know it – it’s My Oracle Support, only from Oracle.Get StartedMy Oracle Support is available as part of your Oracle Premier Support subscription. To get started, visit /support, click on My Oracle Support, and begin reaping the benefits of this exclusive Web support portal.Copyright 2008, Oracle. All Rights Reserved.This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor is it subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.Date: 09/2008。
The Compaq ECO details are as follows:For OpenVMS 7.2-1:s VMS721_SYS-V0600 Alpha V7.2-1 System ECOs OpenVMS VMS721_ACRTL-V0200 Alpha V7.2-1 Compaq C RTL ECOs TCP/IP TCPIPALP_E01A50 TCP/IP for OpenVMS V5.0AFor OpenVMS 7.21-H1:s OpenVMS VMS721H1_UPDATE-V0300 Alpha V7.2-1H1 UPDATE ECOs OpenVMS VMS721H1_ACRTL-V0100 Alpha V7.2-1H1 Compaq C RTL ECOs TCP/IP TCPIPALP_E01A50 TCP/IP for OpenVMS V5.0A ECO These ECOs can be downloaded from the Compaq Services website. Oracle8i Release 3 (8.1.7) Parallel Server makes use TCP/IP services. For more information about configuring and using the TCP/IP feature, please see your OpenVMS system or OpenVMS TCP/IP documentation.Changes from Oracle7Note that Oracle8i Parallel Server has many architectural changes from the version supplied with Oracle 7. Users are urged to review the new features section of the Oracle Parallel Server Concepts and Administration manual for a complete discussion of these changes.The keywords PARALLEL and EXCLUSIVE have been obsoleted from the STARTUP command. In Oracle7, this was reflected in the creation of STARTUP_EXCLUSIVE_<dbname>.COM, STARTUP_EXCLUSIVE_<dbname>.SQL, STARTUP_PARALLEL_<dbname>.COM, and STARTUP_ PARALLEL_<dbname>.SQL files when you set up your Parallel Server instance. Since these keywords have been removed from Oracle 8, now only STARTUP_<dbname>.COM and STARTUP_<dbname>.SQL files are created when you create a new database.Oracle8i Parallel Server requires the installation and operation of the Oracle Group Membership Services daemon. The Daemon must be installed and run on every system where you want to run Parallel Server.The keywords used inside of the init.ora parameter file for Parallel Server have been changed. Users should not simply copy a pre-existing options file into a new installation. Please refer to the Oracle Parallel Server Concepts and Administration manual for complete information on these changes.Because of these changes, a psinit.ora file is no longer created when you create a new database under Oracle8i.Oracle Group Membership ServicesIn the previous versions of Oracle8, only one Oracle Group Membership Services (OGMS) Daemon could be run per system. Since the Oracle Group Membership Services have been incorporated into Oracle8i Parallel Server Instance, this restriction still applies. Only one Oracle8i Parallel Server Instance can be run per system. In addition, only one Oracle8 OGMS daemon, or Oracle8i Parallel Server Instance can be running per system. Each instance or OGMS daemon that runs on a system must be able to access the home and installation directories of the OGMS product area. The OGMS Daemon is a quasi-separate product under Oracle8i. Installation of the Daemon is selected by an option under the Oracle PSOPT Build Options menu of the OpenVMS Oracle installer.The installation procedure for Oracle Group Membership Services runs as an optional part of the Parallel Server Option (PSOPT) installation procedure. The OGMS installation creates a new directory that you specify, and places within it a directory called OGMS.DIR, which is the directory into which OGMS will be installed. In addition, separate directories for each node using this OGMS installation are created as a subdirectory of the OGMS.DIR directory. These directories contain the logs and other files of the OGMS daemons running on the different nodes.You must have the appropriate privilege on your system to create the OGMS installation directories. The directories created will have the ORA_ DBA access right granted to them during installation. This allows any account granted the ORA_DBA access right to administer the OGMS Daemon.The installation procedure creates a define_ file in the OGMS installation directory. This procedure makes the appropriate system-wide definitions necessary to run the OGMS Daemon.Two system wide logical names are defined: OGMS_INSTALL and OGMS_ HOME. The OGMS_INSTALL logical name points at the OGMS.DIR directory created during installation. OGMS_HOME points at one of the per-node subdirectories of the OGMS.DIR directory. For example, if you have a system called AP8VMS, and use the defaults under the PSOPT menu, the following directories and definitions would be made: OGMS_INSTALLasSYS$COMMON:[SYSEXE.ORACLE.OGMS]OGMS_HOMEasSYS$COMMON:[SYSEXE.ORACLE.OGMS.AP8VMS]The define_ file must be run before launching the OGMS Daemon. A reference to this file can be put into your system startup files if you want the definitions to be in effect after a system restart.The OGMS Daemon is controlled by the ogmsctl command. You can start and stop, query the basic status of the Daemon, and get a list of the membership of the OPS cluster with ogmsctl. For more information about the commands available to the OGMS Control program, please see the Oracle Parallel Server Concepts and Administration manual. For Oracle8i the ogmsctl command is not used and should not be invoked.In Oracle8i there is no separate OGMS Daemon process. For previous Oracle8 installations when launched, the OGMS Daemon ran as process ORA_GMS. It was possible to effect the quotas given to this process by defining the appropriate logical name. This has no effect in Oracle8i. Thus, for Oracle8 only, to change the quota of the OGMS process, we define the following system wide logical name:ORA_GMS_PQL$_<quota> <new quota value>For example, to boost BYTLM to 1 million, you would define: $ define/system OGA_GMS_PQL$_BYTLM 1000000Installation of the Oracle Parallel Server optionThe Parallel Server Option is installed by selecting the PSOPT menu choice for the Oracle Installer Build and Load Options menus.Note:You must link the Parallel Server Option into the RDBMSServer before Parallel Server operation is possible. This is done byselecting YES to the question on whether to include the ParallelServer Option in the RDBMS Server Build Options menu.The PSOPT menu choice on the Build Options menu allows you to select a protection mode for the Parallel Server directories, as well as whether you want to install OGMS. The default menu for PSOPT is reproduced below: Note:For Oracle Parallel Server 8.1.7.0 running on AlphaOpenVMS, there is a new default option included in the PSOPTbuild configuration screen. Item number 5 below is the inclusion ofthe parallel server communication option that will be included inyour server.PSOPT Configuration OptionsOptionCurrent Value1. System or Group installation? [S/G] S2. Install Oracle Group Membership Services? Y[Y/N]3. Directory for OGMS install? PTST05:[MJNOEL_816_DROP4A]4. Override previous OGMS installation? [Y/N] Y5. Parallel Server Interprocess Communication TCPpackage (TCP)?Enter (A)LL to select all options.Enter (E)XIT to exit this menu with selected options.Enter (Q)UIT to quit this menu with no action.You may select to have the installer override a current installation, if there are currently definitions of OGMS_INSTALL and OGMS_HOME. If you do not select YES for option 4, then the OGMS installation will fail if these logical names already exist.If you have an OGMS Daemon running already on your system, the installer will create the directories you have indicated, if override is also selected, but it will not override the current definitions of OGMS_INSTALL and OGMS_HOME, nor will it shut down your currently running OGMS Daemon.Please be cautioned that shutting down the OGMS Daemon will terminate any OPS instances running on that system.Given below is the OGMS Installation procedure output for a default installation.------------------------------------------------------ Running ORA_PSOPT_.Building Oracle Group Membership Services.The Oracle Group Membership Services will be installed into an OGMS directory which will be created in a directory that you have specified. Per node directories for each node which uses this installation will be created as OGMS Daemons are launched. Note that this directory must be accessible to all Parallel Server database instances that you wish to run on this node. Also note that all database instances which participate in an OPS cluster must be able to access an OGMS installation. One OGMS Daemon can be run at a time on any cluster node.Creating OGMS directory in SYS$COMMON:[SYSEXE].Creating OGMS install directory SYS$COMMON:[SYSEXE.ORACLE.OGMS].Creating define_.Running define_.Copying files to SYS$COMMON:[SYSEXE.ORACLE.OGMS].Linking OGMS 64 bit daemon- Linking OGMS.EXELinking OGMS 64 bit control program- Linking OGMSCTL.EXESetting protection on OGMS files.Purging OGMS files.OGMS installation complete.--------------------------------------------------------------Reproduced below is the output of the OGMS Installation procedure if the user has selected to override a current installation.---------------------------------------------------------------- Running ORA_PSOPT_.Building Oracle Group Membership Services.An OGMS installation is already present on system AP8VMS.OGMS_INSTALL is currently defined to beSYS$COMMON:[SYSEXE.ORACLE.OGMS].Overriding previous installationThe Oracle Group Membership Services will be installed into an OGMS directory which will be created in a directory that you have specified. Per node directories for each node which uses this installation will be created asOGMS Daemons are launched. Note that this directory must be accessible to all Parallel Server database instances that you wish to run on this node. Also note that all database instances which participate in an OPS cluster must be able to access an OGMS installation. Only one OGMS Daemon can be run at a time on any cluster node.Creating OGMS directory in SYS$COMMON:[SYSEXE].The OGMS directory already exists.Creating define_.Running define_.%DCL-I-SUPERSEDE, previous value of OGMS_INSTALL has been superseded %DCL-I-SUPERSEDE, previous value of OGMS_HOME has been superseded Copying files to SYS$COMMON:[SYSEXE.ORACLE.OGMS].Linking OGMS 64 bit daemon- Linking OGMS.EXELinking OGMS 64 bit control program- Linking OGMSCTL.EXESetting protection on OGMS files.Purging OGMS files.OGMS installation complete.Addition to Createcat ProcedureBefore operating your database in Parallel Server mode, be sure to add the following line to the end of the ora_db:createcat_<dbname>.sql file in your database (ora_db) directory:@ora_rdbms_admin:catparr.sqlIf you have already created the database before adding the reference to catparr, simply do the following:connect internal as sysdba@ora_rdbms_admin:catparr.sqlQuota Considerations for Oracle Parallel ServerOracle8i Parallel Server Option is a completely rearchitected feature from the Parallel Server Option for the Oracle7 Server. Oracle8i now includes a portable Distributed Lock Manager (DLM) internal to the database server. Because of this, the usage of ENQLM quota by the Parallel Server Option has been greatly reduced. Large ENQLM boosts for background processes are no longer necessary in the Oracle8i environment.If you have an Oracle8 Parallel Server installation that uses the new OpenVMS Intra-Cluster Communications (ICC) feature, you should note that ICC buffers are stored in non-paged pool associated with each process. This storage is charged against the process pooled BYTLM quota.In addition, some ICC data is stored in the P1 pool of a process. This storage is allocated by the setting of the CTLPAGES parameter in SYSGEN. The default setting of 256 pages is adequate for many Parallel Server environments. This is not a dynamic parameter, so a change here will require a system reboot.The following formula may be used to estimate the BYTLM and P1 pool requirements for ICC consumption of each process:NCon Number of connectionsNCon * 2048 * 6 bytes of BYTLM quotaNcom * 256 bytes of P1 PoolEach database process connects with the OGMS Daemon. If there are N instances, then N would be the value for NCon.However, Parallel Query Slaves connect in a mesh with all other Parallel Query Slaves. If there are 50 PQS per instance, and four instances, then each PQS will make connections with 200-1 = 199 neighbors.In addition, the Lock Manager Process, LMD0, connects with all other database backgrounds in its instance, as well as with all other LMD0s in the other instances. If there are 4 instances, and each instance has 10 normal backgrounds and 50 Parallel Query Slaves, then the Lock Manger connects with 10 + 50 + 4 + 1 = 65 different processes.Please note that these quota estimates are in addition to quota required by non-Parallel Server functions of the Oracle server.The Process Quota estimation functions of the Oracle Server attempt to make reasonable calculations for the various backgrounds launched during server operations. You can change the quota allocated to a background process by defining certain system logical names before the instance is started.To effect the process quota given to all backgrounds in an instance, define the following:$ define/system ORA_<sid>_PQL$_<quota> <quota_value>If you have a SID named TOM1, and you wish to boost the BYTLM to 2 megabytes, you would use the following:$ define/system ORA_TOM1_PQL$_BYTLM 2000000Or, you could effect the process quota of a particular background by defining the following:$ define/system ORA_<sid>_<process>_PQL$_<quota> <quota_value>If you wanted the LMD0 process of the TOM1 SID to get 3 megabytes of BYTLM, you would use the following:$ define/system ORA_TOM1_LMD0_PQL$_BYTLM 3000000Analyzing OGMS Log filesThe Oracle GMS Daemon creates several files in the OGMS_HOME directory, including Daemon and Control file traces. These files may be useful in debugging OGMS and Parallel Server problems.The following files are created in the OGMS_HOME directory when the OGMS control program starts the OGMS Daemon:ogms_llnmap.dat Local node mapThis is a binary format file which must not bealtered.gms0000.dat Daemon contact informationThis is a binary format file which must not bealtered.cntl_<proc-id>.trc OGMS control program trace fileTraces execution of OGMSCTL command. daem_<proc-id>.trc OGMS daemon trace fileTraces execution of the OGMS daemon.Note:All status codes listed in these trace files by the ICC driverare printed in HEXADECIMAL, not decimal. These values areindicated by the prepending of a "0x" to the data output.There is currently a problem in the ICC support of VMS 7.2 and 7.2-1 such that the ICC system calls can report a status of 25fc(hex), 9724(dec) or:%SYSTEM-F-INSFP1POOL, insufficient process dynamic memorywhen in reality the error is a shortage of BYTLM in the affected process. If this status code is listed in a message showing a status of 294(hex), 660(dec), or:%SYSTEM-F-REJECT, connect to network object rejectedwith a remote status of 25fc(hex), then the affected process is the remote side of the command in question.The BYTLM of the affected process can be increased by defining the proper logical name. Please see the above section "Quota Considerations for Oracle Parallel Server" for more information.It is also possible for the 25fc status to correctly indicate a shortage of P1 pool, in which case you must increase the SYSGEN parameter CTLPAGES and reboot the machines involved.。
ORA-13401: 不受支持的geoimage 格式ORA-13402: NULL 目标ORA-13403: NULL 源几何结构ORA-13404: 不是本地源ORA-13405: NULL 源ORA-13406: 不受支持的图象处理命令[]ORA-13407: 不受认可的空间类型限定词[]ORA-13408: NULL 表名ORA-13409: Oracle 表"" 不存在.ORA-13410: NULL 列名ORA-13411: Oracle 列"" 不存在。
ORA-13412: 无效的ROWIDORA-13413: 无法选择初始化的GeoImageORA-13414: 无法更新包含GeoImage 的表ORA-13415: 无效的域ORA-13416: 无效的几何结构，参数[]ORA-13417: 未定义的模型空间转换光栅ORA-13418: 未定义的光栅空间转换模型ORA-13419: 无效的范围值ORA-13420: 无效的光栅空间转换模型ORA-13421: 无效的模型空间转换光栅ORA-13422: 未初始化的源ORA-13423: 空的来源ORA-13424: 未初始化的目标ORA-13425: 空目标ORA-13426: 不受支持的光栅原点ORA-13427: 未知的光栅原点ORA-13428: 来源不存在ORA-13429: 不支持操作"" (在GeoImage 类型"" 上) ORA-13430: 不支持模型坐标系统ORA-13433: NULL 剪裁方法ORA-13442: 无效缩放参数[] []ORA-13443: 不可识别的缩放模式[]ORA-13451: 不受支持的转换格式[]ORA-13461: 无效的标签/键[]ORA-13462: 无效的连接点ORA-13463: 不受支持的GeoTIFF 几何图形定义ORA-13464: 不受支持的转换ORA-13465: 目标窗口无效ORA-14000: 仅可以指定一个LOCAL 子句ORA-14001: LOCAL 子句与先前指定的GLOBAL 子句相矛盾ORA-14002: 仅可以指定一个GLOBAL 子句ORA-14003: GLOBAL 子句与先前指定的LOCAL 子句相矛盾ORA-14004: 缺少PARTITION 关键字ORA-14005: 缺少RANGE 关键字ORA-14006: 无效的分区名ORA-14007: 缺少LESS 关键字ORA-14008: 缺少THAN 关键字ORA-14009: 可能没有为LOCAL 索引分区指定分区界限ORA-14010: 不可以指定索引分区的此物理属性ORA-14011: 指定给结果分区的名称必须明确ORA-14012: 结果分区名与现有分区名发生冲突ORA-14013: 重复的分区名ORA-14014: 最大的分区列数为16ORA-14015: 分区说明过多ORA-14016: 必须对LOCAL 分区索引的基本表进行分区ORA-14017: 分区界限列表包含的元素过多ORA-14018: 分区界限列表包含的元素太少ORA-14019: 分区范围元素必须是一个: 字符串, 日期时间或间隔文字, 数字或MAXVALUE ORA-14020: 不可以指定表分区的此物理属性ORA-14021: 必须指定所有列的MAXVALUEORA-14022: 不支持LOCAL 分区簇索引的创建ORA-14023: 不支持GLOBAL 分区簇索引的创建ORA-14024: LOCAL 索引的分区数必须等于基本表的分区数ORA-14025: 不能为实体化视图或实体化视图日志指定PARTITIONORA-14026: PARTITION 和CLUSTER 子句互相排斥ORA-14027: 仅可以指定一个PARTITION 子句ORA-14028: 缺少A T 或VALUES 关键字ORA-14029: GLOBAL 分区索引必须加上前缀ORA-14030: CREA TE TABLE 语句中有不存在的分区列ORA-14031: 分区列的类型不可以是LONG 或LONG RAWORA-14032: 分区编号的分区界限过高ORA-14033: ctchvl: 未预期的strdef 类型ORA-14034: ctchvl: 未预期的操作数类型ORA-14035: ctchvl: 未预期的字符串数据类型ORA-14036: 列的分区界限值过大ORA-14037: 分区"" 的分区界限过高ORA-14038: GLOBAL 分区索引必须加上前缀ORA-14039: 分区列必须构成UNIQUE 索引的关键字列子集ORA-14040: 传递给TABLE$OR$INDEX$PART$NUM 的参数个数不当ORA-14041: 可能没有为结果分区指定分区界限ORA-14042: 可能没有为要移动, 修改或重建的分区指定分区界限ORA-14043: 仅可以添加一个分区ORA-14044: 仅可以移动一个分区ORA-14045: 仅可以修改一个分区ORA-14046: 分区可以刚好分成两个新的分区ORA-14047: ALTER TABLE|INDEX RENAME 不可以与其它分区组合ORA-14048: 分区维护操作不可以与其它操作组合ORA-14049: 无效的ALTER TABLE MODIFY PARTITION 选项ORA-14050: 无效的ALTER INDEX MODIFY PARTITION 选项ORA-14051: ALTER MA TERIALIZED VIEW 选项无效ORA-14052: 此上下文中不允许分区扩展表名称语法ORA-14053: 非法尝试修改(在语句中)ORA-14054: 无效的ALTER TABLE TRUNCA TE PARTITION 选项ORA-14055: ALTER INDEX REBUILD 中的关键字REBUILD 必须紧跟<索引名称> ORA-14056: 分区编号: PCTUSED 和PCTFREE 的总和不可以超过100ORA-14057: 分区"": PCTUSED 和PCTFREE 的总和不可以超过100ORA-14058: 分区编号: INITRANS 值必须小于MAXTRANS 值ORA-14059: 分区"": INITRANS 值必须小于MAXTRANS 值ORA-14060: 不可以更改表分区列的数据类型或长度ORA-14061: 不可以更改索引分区列的数据类型或长度ORA-14062: 一个或多个表分区驻留在只读表空间中ORA-14063: 唯一/主约束条件关键字中存在无用索引ORA-14064: 唯一/主约束条件关键字中存在无用分区的索引ORA-14065: 不可以指定分区表的ALLOCATE STORAGEORA-14066: 按索引组织的未分区表的选项非法ORA-14067: 重复的TABLESPACE_NUMBER 说明ORA-14068: 不可以同时指定TABLESPACE 和TABLESPACE_NUMBERORA-14069: 无效的TABLESPACE_NUMBER 值ORA-14070: 仅可以指定分区索引或包含REBUILD 的选项ORA-14071: 用于强制约束条件的索引选项无效ORA-14072: 不可以截断固定表ORA-14073: 不可以截断引导程序表或群集ORA-14074: 分区界限必须调整为高于最后一个分区界限ORA-14075: 分区维护操作仅可以对分区索引执行ORA-14076: DROP/SPLIT PARTITION 不可以应用到LOCAL 索引分区ORA-14078: 您不可以删除GLOBAL 索引的最高分区ORA-14079: 标记为无用索引的分区选项非法ORA-14080: 无法按指定的上限来分割分区ORA-14081: 新分区名必须与旧分区名不同ORA-14082: 新分区名必须与对象的任何其它分区名不同ORA-14083: 无法删除分区表的唯一分区ORA-14084: 您仅可以指定LOCAL 索引的TABLESPACE DEFAULTORA-14085: 分区表不能具有LONG 数据类型的列ORA-14086: 不可以将区索引作为整体重建ORA-14087: 使用<表名> PARTITION (<分区编号>|<赋值变量>) 语法ORA-14088: TABLE$OR$INDEX$PART$NUM 的第二个参数必须是整数常数ORA-14089: 基本表没有对其定义了指定ID 的索引ORA-14090: 必须对索引分区ORA-14091: 必须对表分区ORA-14092: 表达式数不等于分区列数ORA-14093: 表达式的数据类型与分区列的数据类型不兼容ORA-14094: 无效的ALTER TABLE EXCHANGE PARTITION 选项ORA-14095: ALTER TABLE EXCHANGE 要求非分区, 非聚簇的表ORA-14096: ALTER TABLE EXCHANGE PARTITION 中的表必须具有相同的列数ORA-14097: ALTER TABLE EXCHANGE PARTITION 中的列类型或大小不匹配ORA-14098: ALTER TABLE EXCHANGE PARTITION 中的表索引不匹配ORA-14099: 未对指定分区限定表中的所有行ORA-14100: 分区扩展表名不能指远程对象ORA-14101: 分区扩展表名不能指同义字ORA-14102: 仅可以指定一个LOGGING 或NOLOGGING 子句ORA-14104: 不可以指定分区表/索引的RECOVERABLE/UNRECOVERABLEORA-14105: 不可以在此上下文中指定REVERSE/NOREVERSEORA-14106: 不可以指定聚簇表的LOGGING/NOLOGGINGORA-14107: 分区对象要求分区说明ORA-14108: 非法的分区扩展表名语法ORA-14109: 分区扩展对象名仅可以与表一起使用ORA-14110: 分区列不可以是ROWID 类型ORA-14111: 不支持聚簇表中的GLOBAL 分区索引创建ORA-14112: 可能没有为分区或子分区指定RECOVERABLE/UNRECOVERABLE ORA-14113: 分区表不可以具有LOB 数据类型的列ORA-14114: 分区表不能包含具有对象, REF, 嵌套表, 数组等数据类型的列ORA-14115: 分区编号的分区界限过长ORA-14116: 分区"" 的分区界限过长ORA-14117: 分区常驻在脱机表空间中ORA-14118: ALTER TABLE EXCHANGE PARTITION 中的CHECK 约束条件不匹配ORA-14119: 指定的分区界限过长ORA-14120: 没有为DA TE 列完整指定分区界限ORA-14121: MODIFY DEFAULT ATTRIBUTES 不可以与其它操作组合ORA-14122: 仅可以指定一个REVERSE 或NOREVERSE 子句ORA-14123: 重复的NOREVERSE 子句ORA-14124: 重复的REVERSE 子句ORA-14125: 不可以在此上下文中指定REVERSE/NOREVERSEORA-14126: 只有<并行子句> 可遵循结果分区的说明ORA-14127: 非法的索引分区扩展表名语法ORA-14129: INCLUDING INDEXES 必须作为启用UNIQUE 约束条件的表的指定ORA-14130: UNIQUE 约束条件在ALTER TABLE EXCHANGE PARTITION 中不匹配ORA-14131: 启用的UNIQUE 约束条件存在于其中的一个表中ORA-14132: 表不能用于EXCHANGE 中ORA-14133: ALTER TABLE MOVE 不能与其它操作组合ORA-14134: 索引不能同时使用DESC 和REVERSEORA-14135: LOB 列不能用作分区列ORA-14136: ALTER TABLE EXCHANGE restricted by fine-grained securityORA-14150: SUBPARTITION 关键字丢失ORA-14151: 无效的表分区方法ORA-14152: PARTITIONS 子句中指定的分区号无效ORA-14153: 仅可以指定一个STORE IN 或<分区- 说明> 子句ORA-14154: 仅可以指定一个STORE IN 或<子分区- 说明> 子句ORA-14155: PARTITION 或SUBPARTITION 关键字丢失ORA-14156: SUBPARTITIONS 子句中指定的子分区号无效ORA-14157: 无效的子分区名ORA-14158: 子分区说明太多ORA-14159: 重复的子分区名ORA-14160: 该物理属性不能指定给表子分区ORA-14161: 子分区号: PCTUSED 和PCTFREE 的总和不能超过100ORA-14162: 子分区"": PCTUSED 和PCTFREE 的总和不能超过100ORA-14163: 子分区号: INITRANS 值必须少于MAXTRANS 值ORA-14164: 子分区"": INITRANS 值必须少于MAXTRANS 值ORA-14166: 缺失INTO 关键字ORA-14167: 仅可移动一个子分区ORA-14168: 仅可修改一个子分区ORA-14169: 无效的TABLE MODIFY SUBPARTITION 选项ORA-14170: 不能在CREA TE TABLE|INDEX 中指定<分区- 说明> 子句ORA-14171: 不能在CREA TE|ALTER TABLE 中指定<子分区- 说明> 子句ORA-14172: 无效的ALTER TABLE EXCHANGE SUBPARTITION 选项ORA-14173: 非法的子分区扩展的表名语法ORA-14174: 仅<并行子句> 可以跟在COALESCE PARTITION|SUBPARTITION 之后ORA-14175: 子分区维护操作不能与其它操作组合ORA-14176: 该属性不能指定给散列分区ORA-14177: 只能对按散列或组合分区的表上的LOCAL 索引指定STORE-IN (“表空间”列表) ORA-14183: TABLESPACE DEFAULT 仅能对组合的LOCAL 索引指定ORA-14184: 无法在SYSTEM 分区表中创建一个UNIQUE 分区索引ORA-14185: 为该索引分区指定的物理属性不正确ORA-14186: LOCAL 索引的子分区号必须与基于表的子分区号相等ORA-14187: LOCAL 索引的分区方法与基于表的分区方法不一致ORA-14188: 子分区列必须形成UNIQUE 索引的关键字列的子集ORA-14189: 该物理属性不能指定给索引子分区ORA-14190: 仅能指定一个ENABLE/DISABLE ROW MOVEMENT 子句ORA-14191: ALLOCA TE STORAGE 不能为组合范围分区对象指定ORA-14192: 不能修改散列索引分区的物理索引属性ORA-14193: 无效的ALTER INDEX MODIFY SUBPARTITION 选项ORA-14194: 仅能重建一个子分区ORA-14195: 不能为按RANGE 或LIST 分区的对象指定ALLOCA TE STORAGEORA-14240: 对SYSTEM 和范围组合/系统(R+S) 分区方法的语法使用ORA-14241: 无效的表分区方法ORA-14242: 表未被系统或散列方法分区ORA-14243: 表未被范围, 系统或散列方法分区ORA-14244: 对系统或组合范围/系统分区表的非法操作ORA-14251: 指定的子分区不存在ORA-14252: 对散列分区无效的ALTER TABLE MODIFY PARTITION 选项ORA-14253: 表未被组合范围方法分区ORA-14254: 不能为按(组合)“范围”或“列表”分区的表指定ALLOCATE STORAGEORA-14255: 未按范围, 组合范围或列表方法对表进行分区ORA-14256: 无效的结果分区说明ORA-14257: 不能移动范围或散列分区以外的分区ORA-14258: 无效的分区说明ORA-14259: 表未被散列方法分区ORA-14260: 为该分区指定的物理属性不正确ORA-14261: 添加该散列分区时分区界限未指定ORA-14262: 新子分区名必须与旧子分区名不同ORA-14263: 新子分区名必须与所有其它对象的子分区名不同ORA-14264: 表未被组合范围方法分区ORA-14265: 表子分区列的数据类型或长度不能更改ORA-14266: 索引子分区列的数据类型或长度不能更改ORA-14267: 添加(组合) 范围分区时不能指定PARALLEL 子句ORA-14268: 分区的子分区'' 驻留在脱机的表空间中ORA-14269: 不能交换范围或散列分区以外的分区ORA-14270: 未按范围, 散列或列表方法对表进行分区ORA-14271: 表未被组合范围/散列方法分区ORA-14272: 仅能重用有上界的分区ORA-14273: 必须首先指定下界分区ORA-14274: 要合并的分区不相邻ORA-14275: 不能将下界分区作为结果分区重用ORA-14276: EXCHANGE SUBPARTITION 需要非分区的, 非聚簇的表ORA-14277: 在EXCHANGE SUBPARTITION 中的表必须有相同的列数ORA-14278: 列类型或大小在EXCHANGE SUBPARTITION 中不匹配ORA-14279: 索引与ALTER TABLE EXCHANGE SUBPARTITION 中的表不匹配ORA-14280: 表的所有行对指定的子分区不合格ORA-14282: FOREIGN KEY 约束条件在ALTER TABLE EXCHANGE SUBPARTITION 中不匹配ORA-14284: 一个或多个表的子分区驻留在只读表空间中ORA-14285: 不能COALESCE (结合) 该分区的表仅有的分区ORA-14286: 不能COALESCE (结合) 该表分区的表仅有的子分区ORA-14287: 不能REBUILD (重建) 组合范围分区的索引的分区ORA-14288: 索引未被组合范围方法分区ORA-14289: 不能生成不可用的组合范围分区的本地索引ORA-14290: ALTER TABLE EXCHANGE [SUB]PARTITION 中的PRIMARY KEY 约束条件不符ORA-14291: 不能用非分区表EXCHANGE 组合分区ORA-14292: 表的分区类型必须与组合分区的子分区类型相匹配ORA-14293: 分区列数与子分区列数不匹配ORA-14294: 分区数与子分区数不匹配ORA-14295: 分区列和子分区列之间的列的类型和大小不匹配ORA-14296: ALTER TABLE EXCHANGE [SUB]PARTITION 中的表块大小匹配出错ORA-14297: ALTER TABLE EXCHANGE [SUB]PARTITION 中的索引块大小匹配出错ORA-14301: 表级属性必须在分区级属性之前指定ORA-14302: 在语句中仅能指定一个'添加的-LOB-存储器-子句' 的列表ORA-14303: 分区或子分区次序不正确ORA-14304: 列表分区方法需要一个分区列ORA-14305: 列表值'' 在分区'' 中指定了两次ORA-14306: 列表值'' 在分区'', '' 中指定了两次ORA-14307: 分区包含的列表值过多ORA-14308: 分区边界元素必须是字符串, 日期时间或间隔文字, 数值或NULL 之一ORA-14309: 列表值的总数超出了允许的最大值ORA-14310: VALUES LESS THAN 或A T 子句不能与按“列表”分区的表一起使用ORA-14311: 需要VALUES LESS THAN 或A T 子句ORA-14312: 值已经存在于分区中ORA-14313: 值不在分区中ORA-14314: 所得到的“列表”分区必须至少包含1 个值ORA-14315: 不能合并分区自身ORA-14316: 未按“列表”方法对表进行分区ORA-14317: 不能删除分区最后的值ORA-14318: DEFAULT 分区必须是指定的上一分区ORA-14319: DEFAULT 不能使用其他值指定ORA-14320: DEFAULT 不能指定为ADD/DROP VALUES 或SPLITORA-14321: 无法添加/删除DEFAULT 分区的值ORA-14322: DEFAULT 分区已存在ORA-14323: 在DEFAULT 分区已存在时无法添加分区ORA-14324: 所要添加的值已存在于DEFAULT 分区之中ORA-14400: 插入的分区关键字未映射到任何分区ORA-14401: 插入的分区关键字超出指定的分区ORA-14402: 更新分区关键字列将导致分区的更改ORA-14403: 在获得DML 分区锁定之后检测到游标违例ORA-14404: 分区表包含不同表空间中的分区ORA-14405: 分区索引包含不同表空间中的分区ORA-14406: 更新的分区关键字在最高合法分区关键字之外ORA-14407: 分区的表包含在不同表空间中的子分区ORA-14408: 分区的索引包含在不同的表空间中的子分区ORA-14409: 插入的分区关键字在指定的子分区之外ORA-14450: 试图访问已经在使用的事务处理临时表ORA-14451: 不受支持的临时表特性ORA-14452: 试图创建, 更改或删除正在使用的临时表中的索引ORA-14453: 试图使用临时表的LOB，其数据已经被清除ORA-14454: 试图引用引用完整性约束条件中的临时表ORA-14455: 试图在临时表中创建引用完整性约束条件ORA-14456: 不能在临时表中重建索引ORA-14457: 临时表中不允许的VARRAY 和嵌套表列ORA-14458: 试图用INDEX 组织创建临时表ORA-14459: GLOBAL 关键字丢失ORA-14460: 只能指定一个COMPRESS 或NOCOMPRESS 子句ORA-14500: LOCAL 选项没有分区名而无效ORA-14501: 对象未分区ORA-14503: 仅可以指定一个分区名ORA-14504: 语法不支持语法分析ORA-14505: LOCAL 选项仅对分区索引有效ORA-14506: 分区索引要求LOCAL 选项ORA-14507: 分区损坏。
