7 Replies Latest reply: Jan 12, 2010 4:21 AM by 807567 RSS

    errors on /var/adm/messages

    807567
      hi, i have server / HP DL 385 g1/ with solaris 10x86. I have problem with log on messages:

      Jan 23 07:56:15 ora-db1 iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
      Jan 23 07:56:15 ora-db1 iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x42a
      Jan 23 07:56:15 ora-db1 iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x401
      Jan 23 07:56:15 ora-db1 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
      Jan 23 07:56:15 ora-db1 Invalid ioctl opcode = 0x403
      Jan 23 07:56:15 ora-db1 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
      Jan 23 07:56:15 ora-db1 Invalid ioctl opcode = 0x42a
      Jan 23 07:56:15 ora-db1 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
      Jan 23 07:56:15 ora-db1 Invalid ioctl opcode = 0x401

      what is this mesages? and what is help?thanks for any help
        • 1. Re: errors on /var/adm/messages
          807567
          hi, i have a server / Sun Fire X4200 with Solaris 10 x86 11/06 connected to a Sun T3B partner pair with the same error messages.
          I also have Oracle 10g installed.

          Feb 1 13:40:37 gg01 scsi: [ID 243001 kern.warning] : /pseudo/fcp@0 (fcp0)
          Feb 1 13:40:37 gg01 Invalid ioctl opcode = 0x403
          Feb 1 13:40:37 gg01 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
          Feb 1 13:40:37 gg01 Invalid ioctl opcode = 0x42a
          Feb 1 13:40:37 gg01 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
          Feb 1 13:40:37 gg01 Invalid ioctl opcode = 0x401
          Feb 1 13:40:37 gg01 ipf: [ID 872937 kern.notice] NOTICE: Unknown: cmd 0x403 data 8046e5c
          Feb 1 13:40:37 gg01 ipf: [ID 872937 kern.notice] NOTICE: Unknown: cmd 0x42a data 8046ea0
          Feb 1 13:40:37 gg01 ipf: [ID 872937 kern.notice] NOTICE: Unknown: cmd 0x401 data 8046eb4
          • 2. Re: errors on /var/adm/messages
            807567
            I have the same problem on a Sun Fire V240. I also have Oracle 10g installed.

            Feb 15 11:08:07 sapint01 iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
            Feb 15 11:08:07 sapint01 iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x42a
            Feb 15 11:08:07 sapint01 iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x401
            Feb 15 11:08:07 sapint01 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
            Feb 15 11:08:07 sapint01 Invalid ioctl opcode = 0x403
            Feb 15 11:08:07 sapint01 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
            Feb 15 11:08:07 sapint01 Invalid ioctl opcode = 0x42a
            Feb 15 11:08:07 sapint01 scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
            Feb 15 11:08:07 sapint01 Invalid ioctl opcode = 0x401
            Feb 15 11:08:07 sapint01 ipf: [ID 872937 kern.notice] NOTICE: Unknown: cmd 0x403 data ffbfc214
            Feb 15 11:08:07 sapint01 ipf: [ID 872937 kern.notice] NOTICE: Unknown: cmd 0x42a data ffbfc200
            Feb 15 11:08:07 sapint01 ipf: [ID 872937 kern.notice] NOTICE: Unknown: cmd 0x401 data ffbfc1d4
            • 3. Re: errors on /var/adm/messages
              807567
              known oracle bug, contact them for support.

              tim
              • 4. Re: errors on /var/adm/messages
                807567
                sorry hit post too soon

                ask oracle about bugid bug#4955208

                tim
                • 5. Re: errors on /var/adm/messages
                  807567
                  Thanks tim,

                  Too bad that the explanation/solution is only available to "contract users" and not to everyone

                  http://sunsolve.sun.com/search/document.do?assetkey=1-25-84121-1
                  • 6. Re: errors on /var/adm/messages
                    807567
                    I am getting the exact same error, but I am not running Oracle 10g, only running the Oracle agent. Wondering if it's truly caused by an Oracle bug or something related to the fiber adapters or kernel.

                    hostname:/>uname -a
                    SunOS hostname 5.10 Generic_127128-11 i86pc i386 i86pc

                    hostname:/>ps -ef | grep ora
                    oracle 827 1 0 Jun 15 ? 87:13 /opt/app/oracle/product/10.2/agent10g/perl/bin/perl /opt/app/oracle/product/10.
                    oracle 835 827 0 Jun 15 ? 175:20 /opt/app/oracle/product/10.2/agent10g/bin/emagent
                    root 27550 27520 0 09:45:10 pts/1 0:00 grep ora

                    May 7 07:51:35 hostname iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x403
                    May 7 07:51:35 hostname iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x42a
                    May 7 07:51:35 hostname iscsi: [ID 454097 kern.notice] NOTICE: unrecognized ioctl 0x401
                    May 7 07:51:35 hostname scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
                    May 7 07:51:35 hostname Invalid ioctl opcode = 0x403
                    May 7 07:51:35 hostname scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
                    May 7 07:51:35 hostname Invalid ioctl opcode = 0x42a
                    May 7 07:51:35 hostname scsi: [ID 243001 kern.warning] WARNING: /pseudo/fcp@0 (fcp0):
                    May 7 07:51:35 hostname Invalid ioctl opcode = 0x401

                    regards,
                    Will
                    • 7. Re: errors on /var/adm/messages
                      807567
                      The bug number as filed by Oracle is BugID 4955208
                      This bug is specifically found with Oracle Enterprise Manager running on Solaris Operating System.

                      https://metalink.oracle.com/metalink/plsql/per_bug.monitorBug?p_bug_id=4955208

                      Workaround
                      1. Ignore the entries in the messages file, but the files are being filled everyday by the agent.
                      2. If the grid agent is stopped, then it is observed that these messages also disappear.