Error: Operation not allowed for reason code "7" on table SQLSTATE=57016

If you fun Alter Table and then get "Operation not allowed for reason code "7" on table SQLSTATE=57016" Error.

Run "reorg table [table name]" to fix it.

Error: javax.faces.FacesException: No file was uploaded

If you get error like:
javax.faces.FacesException: No file was uploaded
when you try to deploy the jar or war file.
Disk is full it won't be able to do it.
Try to clean /var/tmp folder on Solaris.

Find file on Unix

find /usr -name filename.txt -print

Oracle: ORA-16014: log sequence not archived, no available destinations

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-16014: log 4 sequence# 3874 not archived, no available destinations
ORA-00312: online log 4 thread 1:
'D:\ORACLE\FLASH_RECOVERY_AREA\RTNE\ONLINELOG\O1_MF_4_5BWL0XDH_.LOG'
How to resolve this ?

Firstly, you need to ensure that the log_archive_dest_nn parameters are set up correctly.

Here we have a flash recovery area defined, so we'll just use that.

SQL> alter system set log_archive_dest_10 = 'LOCATION=USE_DB_RECOVERY_DILE_DEST';

System altered.

SQL> alter database open;

Database altered.

To set it in the spfile, use the following:

SQL> alter system set log_archive_dest_10 = 'LOCATION=USE_DB_RECOVERY_DILE_DEST' scope=spfile;

You can also set up any of the other archive log destinations to a valid one. There could be other errors caused by this, which should also point you in the right direction.

SQL> alter system archive log all;
alter system archive log all
*
ERROR at line 1:
ORA-16020: less destinations available than specified by
LOG_ARCHIVE_MIN_SUCCEED_DEST

SQL> show parameter LOG_ARCHIVE_MIN_SUCCEED_DEST

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_min_succeed_dest integer 1

This should not be the issue, but if higher than 1, ensure that enough destinations have been set up.

Also ensure that they are all enabled.

SharePoint: Maximum File Size for Crawling Search Services

Maximum File Size for Crawling Search Services
By default, Search Services can crawl and filter a file with a size of up to 16 megabytes (MB). It will always crawl the first 16MB of a file. After this limit is reached, SharePoint Portal Server enters a warning in the gatherer log “The file reached the maximum download limit. Check that the full text of the document can be meaningfully crawled.” To increase the limit of 16 MB, you must add in the registry new entry MaxDownloadSize. To do this, follow these steps:
Start Registry Editor (Regedit.exe).
Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Global\Gathering Manager
Open Edit - New - DWORD Value. Name it MaxDownloadSize.
Double-click, change the value to Decimal, and type the maximum size (in MB) for files that the gatherer downloads.
Restart the server.
Start Full Crawl.NOTE: Increasing the file size may cause a timeout exception because the crawler can timeout if the file takes too long to crawl/index (because of its size). To increase timeout value, follow these steps...for the full post, check out Maximum File Size for Crawling You can also review searcu usage data by enable search query logging by following these steps:
On the home page, on the Site Actions menu, point to Site Settings, and then clickModify All Site Settings.
On the Site Settings page, under Site Collection Administration, click Site collection usage reports.
On the Site Collection Usage Summary page, on the Quick Launch, click Search queries or Search results.Additional resources: