SP2-0027: Input is too long (> 2499 characters)

SP2-0027: Input is too long (> 2499 characters)

When we tried to execute long SQL queries on the SQLPLUS prompt then we will get the bellow error:

SP2-0027: Input is too long (> 2499 characters)

Error occurred due to SQL queries is not break in different lines it is present in one line which will reached the upper limit of the single line input 2499.

Solution:
To resolve this issue, we will need to break the Single line SQL queries into different line.

In Notepad or Notepad++, we will see the single line SQL queries with wordwrap feature enabled in different line. So we donot know it is in single line or multiple line. Check with disable the wordwrap feature.

We will tried to break it in different line by pressing enter button in between query and break the Single line SQL query into multiple line. So that one line will not reached the upper limit of 2499 character. Then you simply copy paste the SQL queries and execute it directly on SQLPLUS prompt.

Advertisements

One thought on “SP2-0027: Input is too long (> 2499 characters)

  1. Vicken Khachadourian

    I have a set of disks which are used from a Dell EMC V-Block storage system. The disks are partitioned into 128G pieces and we have 8 disks at this point. The systems folks have resized the disks to 256G so that we have more space to work with, but in ASM I still see the disks as 128G instead of the 256G I want to resize the ASM disks to. In other words ASM does not see the change in size of the underlying disk at this point even though in the OS we see the difference. *DATA08 disk is a newly added disk.

    NAME PATH OS_MB TOTAL_MB
    DATA /dev/oracleasm/disks/DATA08 262143 262143
    DATA /dev/oracleasm/disks/DATA06 131071 131071
    DATA /dev/oracleasm/disks/DATA07 131071 131071
    DATA /dev/oracleasm/disks/DATA03 131071 131071
    DATA /dev/oracleasm/disks/DATA02 131071 131071
    DATA /dev/oracleasm/disks/DATA01 131071 131071
    DATA /dev/oracleasm/disks/DATA04 131071 131071
    DATA /dev/oracleasm/disks/DATA05 131071 131071

    What I want to see is something like:

    DATA /dev/oracleasm/disks/DATA08 262143 262143
    DATA /dev/oracleasm/disks/DATA06 262143 131071
    DATA /dev/oracleasm/disks/DATA07 262143 131071
    DATA /dev/oracleasm/disks/DATA03 262143 131071
    DATA /dev/oracleasm/disks/DATA02 262143 131071
    DATA /dev/oracleasm/disks/DATA01 262143 131071
    DATA /dev/oracleasm/disks/DATA04 262143 131071
    DATA /dev/oracleasm/disks/DATA05 262143 131071

    I have attempted to use the ALTER DISKGROUIP DATA RESIZE ALL; and that appears to work but nothing changes. That is the reason that I applied the quarterly patch to fix a bug with the resize.
    There must be something that we are doing wrong with the partitioning of the disk into the parts or there is something we are missing to get ASM to read the disks again and see the disk size changed at the O/S level is my opinion. We can see the disk size changesd at the OS level.
    l
    sblk
    NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
    fd0 2:0 1 4K 0 disk
    sda 8:0 0 256G 0 disk
    └─sda1 8:1 0 128G 0 part
    sdb 8:16 0 256G 0 disk
    └─sdb1 8:17 0 128G 0 part
    sdc 8:32 0 256G 0 disk
    └─sdc1 8:33 0 128G 0 part
    sdd 8:48 0 256G 0 disk
    └─sdd1 8:49 0 128G 0 part
    sde 8:64 0 256G 0 disk
    └─sde1 8:65 0 128G 0 part
    .
    sdi 8:128 0 256G 0 disk
    └─sdi1 8:129 0 256G 0 part

    I am looking for some information to tell me if we should be partitioning the disk in a certain way or there is something we are not doing to get ASM to see those disks with changed storage size.

    Like

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.