Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Syed Saad Ali

Oracle ACE Pro

Oracle Solution Architect

Oracle E-Business Suite

Oracle Cloud Infrastructure

Oracle Fusion Middleware

Oracle Database Administration

Oracle Weblogic Administration

Month: October 2017

October 5, 2017 Office 365 ProPlus Certified with EBS 12.1 and 12.2
NEWS AND UPDATES

Office 365 ProPlus Certified with EBS 12.1 and 12.2

By: Steven Chan| Senior Director

Microsoft Office 365 ProPlus versions of Excel, Word, and Outlook are certified with Oracle E-Business Suite 12.1 and 12.2. See:

This certification includes 32-bit and 64-bit versions of Office 365 ProPlus running on Windows 10, 8.1, and 7.

What is Office 365 ProPlus?

Office 365 ProPlus is a version of Microsoft Office that’s available through Office 365. It includes Word, Excel, Outlook, PowerPoint, Access, OneNote, Publisher, and Skype for Business as well as online services such as Sway and Power Query.

Office 365 ProPlus is installed on the user’s local computer using a streaming and virtualization technology called Click-to-Run. Office 365 ProPlus is not a web-based version of Office. It runs locally on the user’s computer. Users don’t need to be connected to the Internet all the time to use it.

What is not covered by this certification?

EBS 12.1 and 12.2 are certified with the Office 365 ProPlus versions of Excel, Word, and Outlook.

The following Office 365 ProPlus products are not certified with EBS 12.1 or 12.2:

  • Office on iPad and Android devices
  • Office Online browser-based versions of Excel and Word
  • PowerPoint, Access, OneNote, Publisher, and Skype for Business
  • Online services such as Sway and Power Query

Click-to-Run delivers monthly updates to Office 365 ProPlus

By default, Click-to-Run products are configured to be updated automatically every month. Users don’t have to download or install updates. The Click-to-Run product seamlessly updates itself in the background.

Microsoft also offers a semi-annual channel for updates in January and July, as well as a targeted semi-annual channel in March and September.

Certification with Click-to-Run updates

Oracle certified EBS 12.1 and 12.2 in September 2017 with the latest available versions of Excel, Word, and Outlook in Office 365 ProPlus at the time.

Microsoft’s updates to Office 365 ProPlus are intended to be backwards-compatible. This means that Oracle’s certification with the September 2017 baseline should continue to apply to Microsoft updates in October 2017, November 2017, and so on.

It is unlikely that Oracle will be able to certify all monthly Office 365 ProPlus updates with all EBS 12.1 and 12.2 updates. Given Microsoft’s stance towards backwards-compatibility, this is theoretically unnecessary.

It is expected that Oracle will continue to certify selected updates to Office 365 ProPlus versions of Excel, Word, and Outlook with updates to EBS 12.1 and 12.2.

Source: https://blogs.oracle.com/stevenchan/office-365-proplus-certified-with-ebs-121-and-122

 

 

 

October 1, 2017 ORA-01157: cannot identify/lock data file 206 – see DBWR trace file
Errors/Workarounds10gErrors/Workarounds11gErrors/Workarounds12cOracle Database Material

ERROR

ORA-01157: cannot identify/lock data file 206 – see DBWR trace file
ORA-01110: data file 206: ‘+DATA’

SOLUTION

If you are using XML in your database and you are trying to update any XML data, then above error may come.

Step 1: Add below line in your parameter file and bounce the database if not there.

*.dispatchers='(PROTOCOL=TCP) (SERVICE=PRODXDB)’

 

Step 2: Unlock the XDB user if locked.

SQL> alter user XDB account unlock;

 

Step 3:  If you have created a duplicate database or open standby database read/write mode, then source TEMP tablespaces will no more valid. drop your TEMP tablespace and create new TEMP tablespace and make it default.

SQL> DROP TABLESPACE TEMP  INCLUDING CONTENTS AND DATAFILES;

SQL> create temporary tablespace TEMP02 tempfile ‘/u02/apps/ORCL/temp_02.dbf’ size 1024M autoextend on; 

SQL> alter database default temporary tablespace TEMP02;

Bounce the database. Now sure the above error will not come.

 

 

October 1, 2017 ORA-07445: exception encountered: core dump
Errors/Workarounds11gOracle Database Material

ERROR

ORA-07445: exception encountered: core dump
 [kglic0()+756] [SIGSEGV] [ADDR:0x430000010B8AE910] [PC:0x107AB7474] [Address not mapped to object] []
 

SOLUTION

SQL> ALTER SYSTEM SET “_cursor_stats_enabled”=false SCOPE=SPFILE;

Caution : This recommendation can be applied in prod database with Oracle support only. If you are applying it is your own risk.

 

 

October 1, 2017 How to Find and repair Corrupt block in database
Errors/Workarounds10gErrors/Workarounds11gErrors/Workarounds12cOracle Database Material

How to Find and repair Corrupt block in database

Step 1: Below query will show if there is any corrupted block

SELECT * 
FROM   v$database_block_corruption — will show if any corruped block 

Step 2: Below query can give you Detail information about corrupted block:

set head ON; 
set pagesize 2000 
set linesize 250 
SELECT * 
FROM   v$database_block_corruption; 

SELECT e.owner, 
       e.segment_type, 
       e.segment_name, 
       e.partition_name, 
       c.file#, 
       Greatest(e.block_id, c.block#) 
       corr_start_block#, 
       Least(e.block_id + e.blocks  1, c.block# + c.blocks  1) corr_end_block# 
       , 
       Least(e.block_id + e.blocks  1, c.block# + c.blocks  1)  
       Greatest(e.block_id, c.block#) + 1 
       blocks_corrupted, 
       NULL                                                      description 
FROM   dba_extents e, 
       v$database_block_corruption c 
WHERE  e.file_id = c.file# 
       AND e.block_id <= c.block# + c.blocks  1 
       AND e.block_id + e.blocks  1 >= c.block# 
UNION 
SELECT s.owner, 
       s.segment_type, 
       s.segment_name, 
       s.partition_name, 
       c.file#, 
       header_block     corr_start_block#, 
       header_block     corr_end_block#, 
       1                blocks_corrupted, 
       ‘Segment Header’ description 
FROM   dba_segments s, 
       v$database_block_corruption c 
WHERE  s.header_file = c.file# 
       AND s.header_block BETWEEN c.block# AND c.block# + c.blocks  1 
UNION 
SELECT NULL                                                      owner, 
       NULL                                                      segment_type, 
       NULL                                                      segment_name, 
       NULL                                                      partition_name, 
       c.file#, 
       Greatest(f.block_id, c.block#) 
       corr_start_block#, 
       Least(f.block_id + f.blocks  1, c.block# + c.blocks  1) corr_end_block# 
       , 
       Least(f.block_id + f.blocks  1, c.block# + c.blocks  1)  
       Greatest(f.block_id, c.block#) + 1 
       blocks_corrupted, 
       ‘Free Block’                                              description 
FROM   dba_free_space f, 
       v$database_block_corruption c 
WHERE  f.file_id = c.file# 
       AND f.block_id <= c.block# + c.blocks  1 
       AND f.block_id + f.blocks  1 >= c.block# 
ORDER  BY file#, 
          corr_start_block#; 

Step 4:  Collect file ids

SELECT DISTINCT file_id 
FROM   dba_extents; 

Step 5: Collect details 

SELECT file_id, 
       segment_name, 
       segment_type, 
       owner, 
       tablespace_name, 
       block_id, 
       blocks 
FROM   sys.dba_extents 
WHERE  ( file_id BETWEEN 2 AND 19 ) 
       AND 468598 BETWEEN block_id AND block_id + blocks  1;

Step 6:  Repair 

a) Collect all data to temporary table and collect all DDL script and grants.

b) drop the table and re-create it with DDL script. (Disable refence key before drop, enable after create table)

c) Insert all records to the table

Note: This entire activity should not be taken in prod databases without Oracle support’s recommendation.