注册 登录  
 加关注
   显示下一条  |  关闭
温馨提示!由于新浪微博认证机制调整,您的新浪微博帐号绑定已过期,请重新绑定!立即重新绑定新浪微博》  |  关闭

帅小伙的博客

希望能在这里交到更多的朋友

 
 
 

日志

 
 
 
 

linux(AMD64) 从9204到9207升级文档(1)

2006-09-19 13:42:23|  分类: oracle |  标签: |举报 |字号 订阅

  下载LOFTER 我的照片书  |
README for 4163445
linux(AMD64) 从9204到9207升级文档(1) - 帅小伙 - 帅小伙的博客
Patch Details 

Oracle9i

Patch Set Notes

Release 2 (9.2.0.7) Patch Set 6 for Linux x86-64

December 2005

These patch set notes accompany the Oracle9i release 2 (9.2.0.7) patch set.

This document contains the following sections:

1 Patch Set Overview

Patch sets are a mechanism for delivering fully tested and integrated product fixes. Patch sets provide bug fixes only; they do not include new functionality and they do not require certification on the target system.

Patch sets include all of the libraries that have been rebuilt to implement the bug fixes in the set. All of the fixes in the patch set have been tested and are certified to work with each other. Because patch sets include only low impact fixes, you are not required to certify applications or tools against the server unless directed to by the operating system vendor.

Patch sets are cumulative. Patch set release 9.2.0.7 includes all fixes in patch sets 9.2.0.7 and earlier as well as new fixes for patch set 9.2.0.7. This means that unless the patch set documentation indicates otherwise, you can apply this patch set to any earlier release 9.2 installation. You do not have to install intermediate patch sets.

Patch sets contain generic fixes that apply to all platforms. Patch sets may also include additional platform-specific patches.

For a list of products included in this patch set, see the "Patch Set Components" section.

2 Oracle Universal Installer Version Requirements

This patch set includes Oracle Universal Installer release 10.1.0.4. You must use this Oracle Universal Installer to install this patch set and not the Installer from the 9.2.0.x maintenance release media or Oracle home.

This is not a complete software distribution. You must install it in an existing Oracle9i release 2 (9.2.0.x.x) installation. Users applying this patch set must use Oracle Universal Installer release 10.1.0.4 (provided as part of this patch set) or later to ensure that their Oracle home can be patched in the future. Oracle Universal Installer release 10.1.0.4 is also installed when you install this patch set.

3 Patch Set Documentation

There are two documents related to this release of the Oracle9i release 2 patch set:

  • Oracle9i Patch Set Notes, Release 2 (9.2.0.7) Patch Set 6 for Linux x86-64 (this document)

    This document provides:

    • System requirements and information about how to install or reinstall the patch set

    • A list of all bugs fixed to date that are specific to Oracle9i release 2 for Linux x86-64

    • A list of known issues relating to Oracle9i release 2 for Linux x86-64

  • Oracle9i List of Bugs Fixed, Release 2 (9.2.0.7) Patch Set 6

    The List of Bugs Fixed is a list of all generic bugs related to Oracle9i release 2 that have been fixed in this release.

Both of these documents are included with the patch set. The Oracle9i List of Bugs Fixed is also available on OracleMetalink, from document 189908.1, ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts at:

http://metalink.oracle.com    

To locate document 189908.1:

  1. Click Advanced at the top of the OracleMetalink page.

  2. Enter 189908.1 in the Document ID field, then click Submit.

4 System Requirements

The following are the system requirements for this patch set:

  • Operating System

    • SUSE Linux Enterprise Server (SLES) 8 and 9

    • Red Hat Enterprise Linux AS/ES 3


Note:

For all Linux Red Hat AS 2.1, the minimum kernel version requirement is 2.4.9-e.57.

  • Oracle9i

    Oracle9i release 2 (9.2.0.4.0) or later

5 Review Changes in Oracle Text Filtering Technology

Beginning with patch set release 9.2.0.7, INSO software is no longer shipped with Oracle Text. It is replaced with Verity KeyView Export from Verity, Inc. There are a number of differences between the old and the new filters. If you intend to use Oracle Text, review document 296405.1 on the OracleMetalink Web site:

http://metalink.oracle.com    

To locate document 296405.1:

  1. Click Advanced at the top of the OracleMetalink page.

  2. Enter 296405.1 in the Document ID field, then click Submit.

In addition to the platforms listed in document 298017.1, Linux x86-64 also supports Oracle Text filtering technology.

6 Preinstallation Tasks

Complete the following preinstallation tasks before installing the patch set:

6.1 Review Known Preinstallation Issues

Review the information in the following sections. If any of the issues apply to your Oracle installation, follow the instructions before installing the patch set.

6.1.1 Database Upgrade for Oracle E-Business Suite

If you are an Oracle E-Business Suite customer and you want to upgrade your Oracle E-Business Suite release 11i database server to this patch set, then you must check the latest certification status and Interoperability Notes available on the OracleMetaLink Web site at:

http://metalink.oracle.com    

All other customers wanting to upgrade their databases directly to this patch set should read Upgrading Directly to a 9.2.0 Patch Set available on OracleMetalink from document 214887.1.

6.1.2 Upgrade and SYS Schema

This is a generic issue applicable to the upgrade mode, for example, ALTER DATABASE OPEN MIGRATE. During an upgrade from release 9.2.0.1 or later, the catpatch.sql script can take a long time if there are statistics for the SYS schema. Delete the statistics on all of the objects in the SYS schema, and then recollect the statistics after normal database open, if necessary.

To drop and re-create the statistics, enter the following commands in SQL*Plus:

SQL> EXECUTE DBMS_STATS.DELETE_SCHEMA_STATS('SYS');  SQL> EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS('SYS');  

6.1.3 Patch Set Application with Physical or Logical Standby Databases in Place

For information about applying a patch set to a current release of Oracle9i release 2 for a configuration that includes one or more physical standby databases, refer to notes available in OracleMetaLink document 187242.1.

6.1.4 Upgrading Preconfigured Standard Edition Databases

If you are using an Oracle9i release 2 (9.2) preconfigured Standard Edition database, then the database contains the following components that are not supported by the Standard Edition:

  • Oracle Data Mining

  • Oracle OLAP Catalog

  • Oracle OLAP Analytic Workspace

  • Oracle OLAP API

  • Spatial

The catpatch.sql script does not run the patch scripts for these components. It sets the component STATUS to OPTION OFF in the DBA_REGISTRY view. The original versions of the dictionary objects for the components remain in the database but the catpatch.sql script does not apply the patch to them.

6.1.5 Oracle Streams

All databases that use any features of Oracle Streams must be upgraded to release 9.2.0.2 or later. Operation between release 9.2.0.1 and release 9.2.0.2 is not supported for databases using Oracle Streams features.

Before you install the patch set software, review Oracle MetaLink note 283565.1.

6.1.6 Oracle Data Guard

Several known issues relate to the following components of Oracle Data Guard:

  • Redo Apply (Physical Standby Databases)

  • SQL Apply (Logical Standby Databases)

  • Data Guard Broker

  • Data Guard Broker Failover

Refer to OracleMetaLink document 259804.1 for a complete set of release notes applicable to Oracle Data Guard in Oracle9i release 2.

Before you install the patch set software, review Oracle MetaLink note 283565.1.

6.1.7 Oracle Advanced Queuing

Customers running Oracle Applications release 11.5.7 or 11.5.8 with Advanced Queuing configured with multiconsumer queues may encounter corruption problems after upgrading their database to 9.2.0.x from any Oracle8i database.


Note:

Refer to Oracle MetaLink note 231074.1 for more information.

6.1.8 Event 10499: NUMBER Datatypes

Event 10499 was introduced in release 9.2.0.3 to allow customers to revert to the earlier behavior of NUMBER datatypes that have no explicit setting of their scale value. Any nonzero setting of the event level enables the old behavior.

Before the introduction of this event, server code could return zero for the scale if a NUMBER datatype was created without specifying the scale. Other code paths would return -127. With this event, all code paths return -127, as this is the correct behavior.

Client applications may rely on the previous (incorrect) behavior. Typically, client applications will test for a scale of -127 to distinguish between NUMBER and FLOAT datatypes. It is not sufficient to test the scale alone to distinguish between these two datatypes. You must test for a scale of -127 and a nonzero precision to identify a FLOAT.

Client applications that rely on the old behavior can still work as before if the event is set. However, these applications must be corrected before upgrading to the next major release of the Oracle database.

6.1.9 Oracle XDK

The Oracle9i release 2 (9.2.0.7) patch set contains XDK release 9.2.0.9.

6.1.10 XML DB

XML DB users must use DB release 9.2.0.3 or later. Earlier releases are no longer supported.

6.1.11 Building Pro*C Applications if PostgreSQL is Installed

If the postgresql-devel package is installed on the system, add the following directory to the beginning of the SYS_INCLUDE parameter in the $ORACLE_HOME/precomp/admin/pcscfg.cfg file before building Pro*C applications:

$ORACLE_HOME/precomp/public  

6.1.12 PL/SQL Cursor Caching

In release 9.2.0.4 and earlier, the maximum number of cursors that could be cached for fast lookup by PL/SQL was bounded by the value of the OPEN_CURSORS initialization parameter. If you currently have this parameter set to a high value (for example, greater than 1000), it might be causing large numbers of PL/SQL cursors to be cached in the shared pool. This could lead to issues with memory management, frequent reloading of library cache objects, and ORA-04031 errors.

Starting with release 9.2.0.5, the SESSION_CACHED_CURSORS initialization parameter now determines the upper bound for PL/SQL cursor caching instead of the OPEN_CURSORS initialization parameter.

Most users do not need to modify the value of either of these parameters. If the SESSION_CACHED_CURSORS parameter value is greater than the OPEN_CURSORS parameter value, then this change has no performance affect on your system.

However, if the SESSION_CACHED_CURSORS parameter value is zero or a value significantly lower than the OPEN_CURSORS parameter value, and you want to cache PL/SQL cursors for optimal performance, then increase the SESSION_CACHED_CURSORS parameter value appropriately.

This issue is tracked with Oracle bug 3150705.

6.1.13 Oracle Directory Manager is not Supported

This release does not support Oracle Directory Manager, a Java-based tool for administering Oracle Internet Directory. This is due to a Java VM issue with JDK 1.4 on this platform. This issue is tracked with Oracle bug number 2803056.

Use one of the following methods to administer Oracle Internet Directory on this platform, till the patch is available:

  • Use Oracle Directory Manager from 9.2.x release on any other platforms

  • Use command-line tools


See Also:

Oracle Internet Directory Administrator's Guide for further information about how to use command-line tools.

6.2 Preinstallation Considerations for Oracle Real Application Clusters

If you plan to install this patch in an Oracle Real Application Clusters environment, read the following section before proceeding:

6.2.1 Preinstallation Considerations for Oracle Real Application Clusters

This patch set enables you to install the included patches on multiple nodes in a cluster if release 9.2.0.1 or higher is already installed on those nodes. Oracle Universal Installer detects whether the system where you are installing the software is part of a cluster environment. If it is, then the Oracle Universal Installer displays the available nodes from the cluster.


Note:

It is important that you install the patch set on the same set of nodes, which had the base release installation. Choosing a different set of nodes during the patch set installation than were chosen during the base release installation will cause unwanted results in your Real Application Clusters environment, as some nodes will be upgraded to the new software versions, while others will not.

6.3 RAC Only: Configure the hangcheck-timer Kernel Module


Note:

If you have already configured the hangcheck-timer module, for example, if you applied a previous Oracle9i release 2 patch set or installed Oracle9i release 9.2.0.4, you do not need to complete this task.

Starting with release 9.2.0.2, the hangcheck-timer module replaces the watchdog daemon (watchdogd) for RAC installations. The hangcheck-timer module is not required, however Oracle recommends that you use it. The following sections describe the hangcheck-timer module and describe how to configure it.

6.3.1 hangcheck-timer Module

The hangcheck-timer module monitors the Linux kernel for long operating system hangs that could affect the reliability of an RAC node and cause corruption of an RAC database. If the operating system hangs, then the hangcheck-timer module will reboot the node. This approach has the following advantages:

  • Node reboots are triggered from within the Linux kernel, making them less affected by system load.

  • The Oracle Cluster Manager on an RAC node can be stopped and reconfigured because its operation is completely independent of the kernel module.

  • The features in the hangcheck-timer module closely resemble features found in the implementation of Oracle Cluster Manager for RAC on the Microsoft Windows platform, on which Oracle Cluster Manager for Linux x86 was based.

The deprecation and removal of the watchdog daemon requires several parameter changes in the $ORACLE_HOME/oracm/admin/cmcfg.ora file used to configure Oracle Cluster Manager. The changes are as follows:

  • The following parameters in the cmcfg.ora file are no longer valid:

    • WatchdogTimerMargin

    • WatchdogSafetyMargin

    These parameters should be removed from the cmcfg.ora file on all nodes in the cluster.

  • The following configuration parameter has been added to allow the Oracle Cluster Manager to know the name of the hangcheck-timer module so it can be loaded correctly:

    • KernelModuleName

    If the module in the KernelModuleName is correctly specified but not loaded, or is incorrectly specified, then the Oracle Cluster Manager will produce a series of error messages in the system log (/var/log/messages). It will not prevent the process from running. The module must be loaded before you start Oracle Cluster Manager.

  • The CMDiskFile parameter has been changed from optional to mandatory. This ensures a cluster manager quorum partition is used and allows the Oracle Cluster Manager to reliably handle certain hardware and software errors that affect cluster participation.

  • The following configuration parameters have been added to be used when the module is loaded:

    • hangcheck_tick

      This parameter is the interval indicating how often the hangcheck-timer checks on the health of the system.

    • hangcheck_margin

      This parameter sets the margin of error to prevent unnecessary system resets due to certain kernel activities that may randomly introduce delays in the operation of hangcheck-timer.

    Together, these two parameters indicate how long an RAC node must hang before the hangcheck-timer module reboots the system. A node reboot occurs when the system hang time is greater than the sum of the times set in the hangcheck_tick and hangcheck_margin parameters.

6.3.2 Recommended hangcheck-timer Configuration Defaults

The following are the recommended default configuration settings for the hangcheck-timer module. These are in addition to the recommendations for parameters in the RAC documentation.

Parameter Service Setting
hangcheck_tick hangcheck-timer 30 seconds
hangcheck_margin hangcheck-timer 180 seconds
KernelModuleName oracm hangcheck-timer
MissCount oracm hangcheck_tick + hancheck_margin (such as 210 second)

6.3.3 Configure the hangcheck-timer Module

To configure the hangcheck-timer module:

  1. On Red Hat Enterprise Linux 2.1 or SUSE Linux Enterprise Server 8, enter the following command to determine the version of the kernel:

    $ uname -r    

    Note:

    The hangcheck-timer module is available by default with all Red Hat Enterprise Linux 3 and SUSE Linux Enterprise Server 9 installations.

  2. Remove or disable the mechanism that loads the softdog module at system start up, if that module is not used by other software on the node. This is necessary for subsequent steps in the installation process. This step may require log in as the root user.

    One method for setting up previous releases of RAC involved loading the softdog module in the /etc/rc.local file on Red Hat systems or the /etc/init.d/boot.local file on SUSE systems. If this method was used, then remove or comment out the following line in the file:

    /sbin/insmod softdog nowayout=0 soft_noboot=1 soft_margin=60     

    If this method was not used, then check with the system administrator to determine where and how the softdog module is loaded and used. The softdog module is no longer needed in this release of Oracle Cluster Manager.

  3. Remove or disable the mechanism to start the Oracle watchdogd module at system start up. This action is necessary for the subsequent steps in the installation process.

    Check with the system administrator to determine where and how the watchdog daemon is started. If watchdogd is started using an rc script that starts Oracle or Oracle Cluster Manager, then remove or comment out the watchdogd start up in the script. If the watchdog daemon is started by a separate rc script, then ensure the references to this script are removed from the runlevel script directories.

  4. Append the following line to the /etc/rc.local file (Red Hat) or /etc/init.d/boot.local file (SUSE 8):

    /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180     

    For SUSE 9, append the following line to the /etc/init.d/boot.local file:

    /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 hangcheck_reboot=1    
  5. For Red Hat and SUSE 8, load the hangcheck-timer kernel module using the following command as root user:

    # /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180     

    For SUSE 9, load the hangcheck-timer kernel module using the following command as root user:

    # /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180 hangcheck_reboot=1    
  6. Repeat steps 1 through 5 on all RAC nodes where the kernel module must be installed.

  7. Shut down all Oracle services on all RAC nodes, including the following:

    • All Oracle databases using the SQL*Plus commands SHUTDOWN IMMEDIATE and SQL*Plus or SRVCTL.

    • Global Services Daemon using the gsdctl stop command.

    • All running Oracle listeners using the lsnrctl stop command.

    • Oracle Intelligent Agent using the agentctl stop command.

    • Oracle Cluster Manager using the kill or killall command.

    • Oracle watchdogd using the kill or killall command.

      The kill and killall commands imply a full cluster restart because every node will restart when the commands are run if watchdogd is enabled. If one or more nodes restart, then ensure that none of the preceding services are running when the nodes come back up. Shut down any services that start after the restart.

  8. Ensure that the hangcheck-timer module is loaded by running the following command as the root user:

    # /sbin/lsmod | grep hangcheck-timer    

    If the kernel module is not loaded, then load it manually, and check the following line in the /etc/rc.local file (Red Hat) or /etc/init.d/boot.local file (SUSE):

    /sbin/insmod hangcheck-timer hangcheck_tick=30 hangcheck_margin=180     

    Append the line to the appropriate file if necessary.

6.4 RAC Only: Install the Oracle Cluster Manager 9.2.0.7 Patch

Follow the steps in this section to install the Oracle Cluster Manager release 9.2.0.7 patch from a single node of the cluster.


Note:

You must install the Oracle Cluster Manager patch and configure Oracle Cluster Manager before you install the Oracle9i release 2 Database patch set.

Only one instance of Oracle Cluster Manager can run per node. If the system has multiple Oracle home directories, then make sure to apply the patch to the Oracle home directory where Oracle Cluster Manager is installed.


To install the Oracle Cluster Manager release 9.2.0.7 patch:

  1. Log in to an RAC node as the oracle user.

  2. If you are not installing the software on the local system, enter the following command to direct X applications to display on the local system:

    • Bourne, Bash, or Korn shell:

      $ DISPLAY=local_host:0.0 ; export DISPLAY    
    • C shell:

      % setenv DISPLAY local_host:0.0    

    In this example, local_host is the host name or IP address of the system that you want to use to display the Installer (your workstation or PC).

  3. Ensure that the ORACLE_HOME environment variable is set correctly.

  4. Change directory to the Disk1 directory where you unpacked the patch set file.

  5. Start the Installer as follows:


    Note:

    Make sure that you run the Installer from the Disk1/oracm directory, and not from the Disk1 directory.

    $ ./oracm/runInstaller    

    The Welcome screen appears.

  6. Click Next.

    The Specify File Locations screen appears.

  7. Specify the Oracle home name and path, then click Next.

  8. Verify the information displayed, then click Install.

    The Oracle Cluster Manager patch will install the latest OUI on the primary node. After the software has been installed, the End of Installation screen appears.

  9. Enter the following commands where oracle_home is the Oracle home where you installed Oracle Universal Installer 10.1.0.4:

    $ cd oracle_home/oui/bin  $ ./runInstaller -updateNodeList -noClusterEnabled -local ORACLE_HOME=$ORACLE_HOME CLUSTER_NODES=node1,node2,node3    
  10. Click Exit, then click Yes to exit from the Installer.

6.5 RAC Only: Configure Oracle Cluster Manager to Use the hangcheck-timer Module


Note:

If you have already configured Oracle Cluster Manager to use the hangcheck-timer module, for example, if you applied a previous patch set or installed Oracle9i release 9.2.0.4, you do not need to complete this task.

Configure Oracle Cluster Manager to use the hangcheck-timer module on all cluster nodes as follows:

  1. Make any necessary changes to the $ORACLE_HOME/oracm/admin/cmcfg.ora file. The changes include the following:

    • Remove any lines containing WatchdogSafetyMargin and WatchdogTimerMargin.

    • Adjust the value of the MissCount line based on the sum of the hangcheck_tick and hangcheck_margin values. The default value is 210.

    • Verify that a valid CmDiskFile line exists in the following format:

      CmDiskFile=file_or_raw_device_name    

      In the preceding example, the file or raw device must be valid. If you specify the name of a file that does not exist, then the file is created if the base directory exists. If you specify a raw device, then that raw device must exist and have the correct ownership and permissions.

    • Add the following KernelModuleName line:

      KernelModuleName=hangcheck-timer    
  2. Modify the ocmstartup.sh and ocmargs.ora scripts to remove any watchdogd information, if they are used for start up.

    • Remove the words watchdogd and from the line Sample startup script for watchdogd and oracm in the $ORACLE_HOME/oracm/bin/ocmstart.sh script.

    • Remove all lines that contain watchdogd, both uppercase and lowercase, from the rest of the $ORACLE_HOME/oracm/bin/ocmstart.sh script.

    • Remove the first line that contains watchdogd from the $ORACLE_HOME/oracm/admin/ocmargs.ora script.

  3. Perform the following step if you are using a cluster file system (CFS) for the Quorum disk.

    1. Log in as the root user.

    2. Run the following command:

      # dd if=/dev/zero of=quorum_disk_file bs=4096 count=65    

      In this command, the CmDiskFile parameter in the $ORACLE_HOME/oracm/admin/cmcfg.ora file lists the file name used for the quorum_disk_file.

  4. Restart Oracle Cluster Manager on all RAC nodes.

  5. Make sure that Oracle Cluster Manager is running, and that the watchdog daemon process (watchdogd) is not running on all nodes before applying the database patch set.

6.6 Identify the Oracle9i Installation

This is not a complete software distribution. You must install it in an existing Oracle9i Oracle home. To identify Oracle home directories, view the /etc/oratab file.

If you are installing this patch set on an existing Real Application Clusters (RAC) installation, you must run the Installer from the same node from which you performed the initial installation.

6.7 Check Postrelease Updates

Before installing this patch set in a production environment, review document 189908.1, ALERT: Oracle9i Release 2 (9.2) Support Status and Alerts, available on the OracleMetaLink Web site at:

http://metalink.oracle.com    

To locate this document:

  1. Click Advanced at the top of the OracleMetalink page.

  2. Enter 189908.1 in the Document ID field, then click Submit.

This document is created by Oracle Support Services and provides information about the status of issues discovered after this patch set was released. If you are unable to access this site, then contact Oracle Support Services before installing this patch set in a production environment.

6.8 Download and Extract the Installation Software

To download and extract the patch set installation software:

  1. Download and extract the p4163445_9207_AMD.zip patch set installation archive to a directory that is not the Oracle home directory or under the Oracle home directory. For example, Oracle_patch.

  2. Enter the following commands to unzip and extract the installation files:

    $ unzip p4163445_9207__AMD.zip    

6.9 Set the ORACLE_HOME and ORACLE_SID Environment Variables

Enter the following commands to set the ORACLE_HOME and ORACLE_SID environment variables:

  • Bourne, Bash, or Korn shell:

    $ ORACLE_HOME=oracle_home  $ ORACLE_SID=sid  $ export ORACLE_HOME ORACLE_SID    
  • C shell:

    % setenv ORACLE_HOME oracle_home  % setenv ORACLE_SID sid    

In these examples, oracle_home is the Oracle home directory where the Oracle9i installation that you want to upgrade is installed, and sid is the SID of the database that you want to upgrade.

6.10 Shut Down Oracle Databases

Shut down any existing Oracle database instances with normal or immediate priority. On RAC systems, shut down all instances on each node.

6.11 Stop All Processes

Stop all listener and other processes running in the Oracle home directory where you want to install the patch set.

6.12 Back Up the System

Oracle recommends that you create a backup of the Oracle9i installation before you install the patch set.

6.13 Configuring Kernel Parameters

After updating the values of kernel parameters in the /etc/sysctl.conf file, ensure that you either reboot the computer or run the sysctl -p command to make the changes of the /etc/sysctl.conf file available in the active kernel memory.

On SUSE Linux Enterprise Server 9.0, ensure that you set the following kernel parameter:

disable_cap_mlock = 1  
  评论这张
 
阅读(228)| 评论(0)
推荐 转载

历史上的今天

评论

<#--最新日志,群博日志--> <#--推荐日志--> <#--引用记录--> <#--博主推荐--> <#--随机阅读--> <#--首页推荐--> <#--历史上的今天--> <#--被推荐日志--> <#--上一篇,下一篇--> <#-- 热度 --> <#-- 网易新闻广告 --> <#--右边模块结构--> <#--评论模块结构--> <#--引用模块结构--> <#--博主发起的投票-->
 
 
 
 
 
 
 
 
 
 
 
 
 
 

页脚

网易公司版权所有 ©1997-2018